Processing commands for cont...@bugs.debian.org:
> severity 703092 critical
Bug #703092 [dpkg] dpkg --set-selections ignores available packages never
installed or removed by dpkg
Severity set to 'critical' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Processing control commands:
> tags -1 - wheezy sid
Bug #703696 [pgpool2] pgpool2: PID file assumes PostgreSQL is installed
Removed tag(s) sid and wheezy.
--
703696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703696
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
-
Control: tags -1 - wheezy sid
On Wed, 2013-04-10 at 00:33 +, Debian Bug Tracking System wrote:
> > tags 703696 wheezy sid
> Bug #703696 [pgpool2] pgpool2: PID file assumes PostgreSQL is installed
> Added tag(s) sid and wheezy.
The BTS already knows that due to version tracking (and the packag
On Tuesday, April 09, 2013 07:29:24 PM you wrote:
> Tags: patch
>
> The following patch to pgpool2's init script makes
> sure /var/run/postgresql exists and sets proper permissions so it works
> with and without PostgreSQL coexisting on the same machine.
If postgresql isn't installed, how does th
I had a similar problem (using a thinkpad x220). Upgrading to the 3.8
kernel (linux-image-3.8-...) fixed this issue for me.
On 04/08/2013 04:38 PM, Kees de Jong wrote:
> Please supply the following logs.
>
> ~/.xsession-errors
> /var/log/syslog
> /var/log/Xorg.0.log
>
> My best guess is that this
On 07/04/13 19:26, Michael Biebl wrote:
> [Please CC the bug submitter in your reply, if you expected them to answer]
>
> FWIW, a simple recompilation against xulrunner 20.0 was sufficient to
> make the extension work again, so requesting a binNMU could be all that
> is needed.
>
> That said, I s
Processing commands for cont...@bugs.debian.org:
> tags 703696 wheezy sid
Bug #703696 [pgpool2] pgpool2: PID file assumes PostgreSQL is installed
Added tag(s) sid and wheezy.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
703696: http://bugs.debian.org/cgi-bin/bu
Tags: patch
The following patch to pgpool2's init script makes
sure /var/run/postgresql exists and sets proper permissions so it works
with and without PostgreSQL coexisting on the same machine.
--
Prof. Ernesto Hernández-Novich - MYS-220C - @iamemhn
Geek by nature, Linux by choice, Debian of cou
Processing commands for cont...@bugs.debian.org:
> found 704625 libapache-mod-security/2.5.12-1
Bug #704625 {Done: Alberto Gonzalez Iniesta }
[modsecurity-apache] modsecurity-apache: CVE-2013-1915: Vulnerable to XXE
attacks
Marked as found in versions libapache-mod-security/2.5.12-1.
> thanks
St
Hi,
On Tue, Apr 09, 2013 at 06:17:00PM +0200, David Kalnischkies wrote:
> I have done very few tests, but it seems like bringing openoffice.org-core
> back (as a transitional package) is the simplest workaround. If I remember
> right all status-files I have seen so far about this issue (not that m
Your message dated Tue, 09 Apr 2013 19:32:53 +
with message-id
and subject line Bug#704850: fixed in pango1.0 1.32.5-4
has caused the Debian Bug report #704850,
regarding libpango1.0-0: i386 packages do not recognize new "all" arch package
on multiarch, want older i386 specific package instal
Your message dated Tue, 09 Apr 2013 19:32:53 +
with message-id
and subject line Bug#704850: fixed in pango1.0 1.32.5-4
has caused the Debian Bug report #704850,
regarding libpango1.0-0:all 1.32.5-3 (Multi-Arch: no) is not co-installable
with libpango1.0-0
to be marked as done.
This means tha
Your message dated Tue, 09 Apr 2013 19:32:53 +
with message-id
and subject line Bug#704795: fixed in pango1.0 1.32.5-4
has caused the Debian Bug report #704795,
regarding libpango1.0-0: i386 packages do not recognize new "all" arch package
on multiarch, want older i386 specific package instal
Your message dated Tue, 09 Apr 2013 19:32:53 +
with message-id
and subject line Bug#704795: fixed in pango1.0 1.32.5-4
has caused the Debian Bug report #704795,
regarding libpango1.0-0:all 1.32.5-3 (Multi-Arch: no) is not co-installable
with libpango1.0-0
to be marked as done.
This means tha
Processing commands for cont...@bugs.debian.org:
> # Non-regression FTBFS aren't RC
> severity 705050 important
Bug #705050 [src:libpyzy] libpyzy: FTBFS when char is unsigned
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Processing commands for cont...@bugs.debian.org:
> # Non-regression FTBFS aren't RC
> severity 705058 important
Bug #705058 [src:libpyzy] libpyzy: FTBFS on non-amd64: symbols not as expected
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you nee
Your message dated Tue, 09 Apr 2013 17:48:51 +
with message-id
and subject line Bug#704111: fixed in llvm-toolchain-3.2 1:3.2repack-1~exp4
has caused the Debian Bug report #704111,
regarding clang fails to correctly implement hard float ABI during default
compiles due to rediculously low defa
Processing commands for cont...@bugs.debian.org:
> reopen 704252
Bug #704252 {Done: Michael Gilbert } [fpc] [fpc] Builds
binaries not listed in debian/control
Bug reopened
Ignoring request to alter fixed versions of bug #704252 to the same values
previously set
> thanks
Stopping processing here.
reopen 704252
thanks
The bug exists really. You just need to have a look at debian/rules:172
and will see that the debian/control file is systematically rewritten.
Of course it happens that current version of debian/control committed in
svn exactly matches the output of fixdeb, but this does not m
Package: iceweasel
Version: 20.0-1
Severity: serious
Tags: upstream patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Attachment https://bug814693.bugzilla.mozilla.org/attachment.cgi?id=698508
of upstream bug report https://bugzilla.mozilla.org/show_bug.cgi?id=814693
fixes this and makes icewe
On Thu, Apr 4, 2013 at 10:46 PM, Julien Cristau wrote:
> On Sun, Mar 24, 2013 at 18:17:46 +0100, David Kalnischkies wrote:
>
>> Pictures^Wdpkg-status files or it didn't happen, as I said multiple times
>> now.
>>
> You'll find the (compressed) status file attached.
[…]
> E: Could not perform imme
Hi,
Carlos Alberto Lopez Perez writes:
> Now I'm convinced that the right fix for this is to revert upstream
> d769529a71ccda4e833f919f3c5693d25b005ff0 [1] commit on libgcrypt like
> Ubuntu did.
>
> The Regression introduced on python-gnutls by such reversion was already
> fixed on Ubuntu with a
Processing commands for cont...@bugs.debian.org:
> forwarded 704645 https://bugs.g10code.com/gnupg/msg4558
Bug #704645 [gnupg] gpg --verify suggests entire file was verified, even if
file contains auxiliary data
Set Bug forwarded-to-address to 'https://bugs.g10code.com/gnupg/msg4558'.
> thanks
St
Source: libpyzy
Version: 1.0.1-1
Severity: serious
Justification: fails to build from source
Builds of libpyzy on architectures other than amd64 and kfreebsd-amd64
that get past #705050 have been failing due to platform-specific
variation in mangled symbol names (and formal types, presumably).
Cou
Processing control commands:
> notfound -1 1:1.12.13-12+squeeze1
Bug #659861 [cvs] cvs contains /usr/share/info/dir.gz
Bug #664872 [cvs] cvs: Excess dir.gz file in /usr/share/info
No longer marked as found in versions cvs/1:1.12.13-12+squeeze1.
No longer marked as found in versions cvs/1:1.12.13-1
Control: notfound -1 1:1.12.13-12+squeeze1
On Fri, 2013-04-05 at 17:16:47 +0200, Guillem Jover wrote:
> Control: fixed -1 1:1.12.13-12+squeeze1
> It's closed, but marked as still affecting the version in stable.
> I think the above should fix that.
Nope, I guess this one should do, though:
<
Processing commands for cont...@bugs.debian.org:
> found 704625 2.5.12-1
Bug #704625 {Done: Alberto Gonzalez Iniesta }
[modsecurity-apache] modsecurity-apache: CVE-2013-1915: Vulnerable to XXE
attacks
There is no source info for the package 'modsecurity-apache' at version
'2.5.12-1' with archit
Source: libpyzy
Version: 1.0.1-1
Severity: serious
Justification: fails to build from source
Builds of libpyzy on architectures in which the standard char type is
unsigned have been failing:
DoublePinyinTable.h:376:1: error: narrowing conversion of
'-0x1' from 'int' to 'const cha
Hi,
On Sat, Apr 06, 2013 at 08:00:56PM -0400, Michael Gilbert wrote:
> Package: opus
> Severity: serious
> Version: 0.9.14+20120615-1
> Tags: security
>
> Hi,
> the following vulnerability was published for opus.
So ... I'm not particularly convinced that this issue is actually 'serious'
in th
Processing commands for cont...@bugs.debian.org:
> severity 705040 important
Bug #705040 [virtaal] virtaal: Can not open any file
Severity set to 'important' from 'grave'
> tags 705040 unreproducible
Bug #705040 [virtaal] virtaal: Can not open any file
Added tag(s) unreproducible.
> thanks
Stoppin
severity 705040 important
tags 705040 unreproducible
thanks
Quoting Vincent Lhote (deb...@vincent.lhote.name):
> Package: virtaal
> Version: 0.7.1-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> When opening any po file, including the tutorial one, the prog
Andreas Beckmann writes:
> On 2013-04-09 12:29, Arnaud Patard wrote:
>
>>> The postinst I don't really get - why are there that many rm's on
>>> configuration files?
>>
>> The files (for now) are created by waagent. This means:
>> - if the package is removed (but not purged), we won't be able to
Am 09.04.2013 00:36, schrieb Klaus Ethgen:
> Package: gvfs
> Severity: critical
>
> Sorry for the high severity but it breaks the system in a very hard way,
> breaking the hardware cdrom tray and harming humans.
>
> The problem is that when I open the cd tray to insert a cd, gvfs has
> installed
Processing commands for cont...@bugs.debian.org:
> severity 704950 minor
Bug #704950 [logrotate] logrotate: Errors "last rotated in the future --
rotation forced"
Severity set to 'minor' from 'grave'
> retitle 704950 logrotate: Error and forced rotation if timezone change moves
> localtime date
severity 704950 minor
retitle 704950 logrotate: Error and forced rotation if timezone change moves
localtime date backwards a day
thanks
On Mon, Apr 08, 2013 at 08:20:49PM +0200, Vincent Lefevre wrote:
> severity 704950 grave
> done
>
> because obvious critical data loss (though the case is not
Package: virtaal
Version: 0.7.1-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
When opening any po file, including the tutorial one, the program refuse to
open it and states:
DatabaseError: database disk image is malformed
The last time I used the software, in 2012
On 2013-04-09 12:29, Arnaud Patard wrote:
>> The postinst I don't really get - why are there that many rm's on
>> configuration files?
>
> The files (for now) are created by waagent. This means:
> - if the package is removed (but not purged), we won't be able to purge
> it by using waagent -uni
Andreas Beckmann writes:
Hi,
> Package: waagent
> Version: 1.2-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts I noticed your package fails to remove.
>
>>From the attached log (scroll to the bottom...):
>
> Removing waagent
Quoting Cyril Brulebois (k...@debian.org):
> Christian PERRIER (09/04/2013):
> > After some resyncing in master (it still had the "drop menu" change),
> > I come up with the attached debdiff wrt 3.14+nmu1.
>
> Couldn't we just pretend 3.14+nmu1 never happened? See below.
I'm lost...:-)
The one
On Tue, Apr 9, 2013 at 12:11:06 +0200, Cyril Brulebois wrote:
> > + * Drop menu from the desktop task. Closes: #699390
>
> 6 months into the freeze? I'm not sure we want that at this point,
> but I won't stop release managers from asking for its being merged
> if they were so inclined.
>
Relea
Christian PERRIER (09/04/2013):
> After some resyncing in master (it still had the "drop menu" change),
> I come up with the attached debdiff wrt 3.14+nmu1.
Couldn't we just pretend 3.14+nmu1 never happened? See below.
> Basically:
>
> [ Christian Perrier ]
> * Add iw package to Recommends
On Tue, Sep 25, 2012 at 12:04:59PM -0400, Aaron M. Ucko wrote:
> Package: liburcu1
> Version: 0.7.4-1
> Severity: serious
> Justification: Policy 8.6
This is a bug report against liburcu/0.7.4-1 but you seem to have closed
it in an ltt-control upload. If it wasn't a liburcu bug in the first
place,
Package: liburcu
Version: 0.7.6-1
Severity: serious
Hi,
Your package seems to be marked Architecture: any but seems to FTBFS on
multiple architectures, some of them even release architectures. mipsel
has already been marked as Not-For-Us.
One of them is sparc which built for 0.6.7-1 but has fail
Quoting Steven Chamberlain (ste...@pyro.eu.org):
> Control: tags -1 = d-i patch
>
> On 08/04/13 16:21, Julien Cristau wrote:
> > AFAIK that has been reverted.
>
> Oh it has, thanks. The purpose of the branches makes sense now.
>
> Attached is a patch for master, and with the right bug number th
Processing commands for cont...@bugs.debian.org:
> severity 704795 serious
Bug #704795 [libpango1.0-0] libpango1.0-0: i386 packages do not recognize new
"all" arch package on multiarch, want older i386 specific package installed
Severity set to 'serious' from 'normal'
> forcemerge 704795 704850
B
Processing commands for cont...@bugs.debian.org:
> close 704808 4.0~a14-1
Bug #704808 [live-image-all,live-images] live-images and live-image-all: error
when trying to install together
There is no source info for the package 'live-image-all' at version '4.0~a14-1'
with architecture ''
There is n
On Mon, 8 Apr 2013, Filipus Klutiero wrote:
> It seems easy to workaround by modifying that file to support a double
> inclusion.
Probably.
> mediawiki-extensions-base currently provides 2 extensions which provide
> Special:Interwiki: the old extension, SpecialInterwiki, and the new extension,
>
I would recommend to NOT USE php from experimental if you need to rely on it.
The version in experimental is not intended to be used for anything than
testing.
—
Ondřej Surý
On Sun, Apr 7, 2013 at 1:33 PM, Riaas Mokiem wrote:
> I also had this problem, so I was happy to see it was already fix
48 matches
Mail list logo
