Hi,
> Given the only {build-,}reverse dependencies for this package are
> gitalist and gitalist-common, that were themselves removed from
> testing for the very same reason (not updated for current Catalyst),
> I suggest we remove libcatalyst-view-component-subinclude-perl from
> testing too, and
Ben Hutchings writes:
> 'iocharset=iso8859-1' is actually the default; you would need to
> override the default by specifying 'iocharset=utf8'.
Ah, right. Yes, in that case I agree we can just lose the explicit
iocharset setting in elilo.sh.
> I can reassign this to elilo and you can set sever
Processing commands for cont...@bugs.debian.org:
> reassign 685186 elilo
Bug #685186 [src:linux] IA64 (Itanium) Wheezy, ELILO installation failed
Bug reassigned from package 'src:linux' to 'elilo'.
No longer marked as found in versions linux/3.2.23-1.
Ignoring request to alter fixed versions of bu
Processing commands for cont...@bugs.debian.org:
> forwarded 690741 https://bugzilla.gnome.org/show_bug.cgi?id=686258
Bug #690741 [evolution] evolution corrupts any mboxes with "From_" lines
Set Bug forwarded-to-address to
'https://bugzilla.gnome.org/show_bug.cgi?id=686258'.
> stop
Stopping proce
Package: evolution
Severity: critical
Tags: upstream
Justification: causes serious data loss
Hi.
This is rather a warning for all Debian users. the bug is already reported
upstream.
Today I found a critical bug in Evolution that corrupts any mails when using
the mbox format (either by exportin
Processing commands for cont...@bugs.debian.org:
> notfixed 634533 1:9.7.3-1ubuntu2
Bug #634533 {Done: Michael Gilbert } [src:bind9] bind9:
FTBFS: configure: error: could not find Berkeley DB include directory
Bug #645287 {Done: Michael Gilbert } [src:bind9] FTBFS:
could not find Berkeley DB inc
Your message dated Tue, 16 Oct 2012 21:11:13 -0400
with message-id
and subject line re: bind9: FTBFS: configure: error: could not find Berkeley DB
include directory
has caused the Debian Bug report #634533,
regarding bind9: FTBFS: configure: error: could not find Berkeley DB include
directory
t
Your message dated Tue, 16 Oct 2012 21:11:13 -0400
with message-id
and subject line re: bind9: FTBFS: configure: error: could not find Berkeley DB
include directory
has caused the Debian Bug report #634533,
regarding FTBFS: could not find Berkeley DB include directory
to be marked as done.
This
On Tuesday, October 16, 2012 11:52:47 Anton Gladky wrote:
> I am not able to reproduce the bug.
> Tested platforms: i386, armel and amd64 (VM)
I also can't reproduce this on any of my machines (i386 and amd64).
If you (Julius, or anybody else) can get it to fail, it might help to
include some mo
Lucas Nussbaum wrote (08 Jul 2012 17:09:35 GMT) :
>> Test Summary Report
>> ---
>> t/01-app.t (Wstat: 256 Tests: 1 Failed: 1)
>> Failed test: 1
>> Non-zero exit status: 1
>> Files=2, Tests=7, 1 wallclock secs ( 0.01 usr 0.02 sys + 1.13 cusr 0.12 csys
>> = 1.28
>> CPU)
>> Resul
Your message dated Tue, 16 Oct 2012 20:47:53 +
with message-id
and subject line Bug#690672: fixed in librdmacm 1.0.16-1
has caused the Debian Bug report #690672,
regarding librdmacm: CVE-2012-4516
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Tue, 16 Oct 2012 20:47:45 +
with message-id
and subject line Bug#640874: fixed in leave 1.12-2.1
has caused the Debian Bug report #640874,
regarding leave: debian/rules is not a Makefile
to be marked as done.
This means that you claim that the problem has been dealt with.
I
Processing commands for cont...@bugs.debian.org:
> block 690730 with 690632
Bug #690730 [release.debian.org] unblock: solarpowerlog/0.23a-2
690730 was not blocked by any bugs.
690730 was not blocking any bugs.
Added blocking bug(s) of 690730: 690632
> thanks
Stopping processing here.
Please conta
Processing commands for cont...@bugs.debian.org:
> reopen 686861
Bug #686861 {Done: Cyril Brulebois } [src:debian-installer]
debian-installer: kfreebsd requires larger MFS_ROOT
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may
reopen 686861
notfixed 686861 20120930
found 686861 20120930
severity 686861 wishlist
thanks
Hi,
I'm sorry to be a nuisance, but could the MFSROOT_LIMIT perhaps be
lowered just slightly, to 80 MiB?
The increase above 64 MiB was necessary because the installer (only
momentarily) seems to need a l
On mar., 2012-10-16 at 17:17 +0200, Paul Menzel wrote:
> and logging out or restarting the system started LightDM up as
> expected.
> So I think it is safe to implement that change.
Ok, thanks for the test. I confirmed with gdm3 maintainers that they use
Xorg command, not X, so I guess it makes s
Processing commands for cont...@bugs.debian.org:
> tags 690632 + pending
Bug #690632 [solarpowerlog] solarpowerlog: bashism in /bin/sh script
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
690632: http://bugs.debian.org/cgi-bin/bugreport.cgi
Your message dated Tue, 16 Oct 2012 19:47:52 +
with message-id
and subject line Bug#690658: fixed in torbutton 1.4.6.3-1
has caused the Debian Bug report #690658,
regarding xul-ext-torbutton: incompatible with iceweasel 10.0.8-ESR and later
to be marked as done.
This means that you claim that
On Thu, 11 Oct 2012, Sébastien Villemot wrote:
Thanks for your reply. I have rescheduled the upload to DELAYED/5, so
that you can make an upload of your own this weekend.
I failed to do this because I got stuck figuring out what was up with the
large number of Ubuntu bugs. I think we have mor
Your message dated Tue, 16 Oct 2012 19:32:45 +
with message-id
and subject line Bug#688713: fixed in timidity 2.13.2-40.1
has caused the Debian Bug report #688713,
regarding timidity-daemon: mishandles conffiles
to be marked as done.
This means that you claim that the problem has been dealt w
Processing commands for cont...@bugs.debian.org:
> # Tuesday 16 October 19:03:10 UTC 2012
> # Tagging as pending bugs that are closed by packages in NEW
> # http://ftp-master.debian.org/new.html
> #
> # Source package in NEW: ibus-libpinyin
> tags 689963 + pending
Bug #689963 [wnpp] ITP: ibus-lib
Processing commands for cont...@bugs.debian.org:
> forwarded 685812 http://projects.scipy.org/numpy/ticket/2228
Bug #685812 [python-numpy] ABI change in 1.6.1 version
Set Bug forwarded-to-address to 'http://projects.scipy.org/numpy/ticket/2228'.
> thanks
Stopping processing here.
Please contact m
Hi,
I am not able to reproduce the bug.
Tested platforms: i386, armel and amd64 (VM)
Thanks,
Anton
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
FACULTY/DEPART./ADMIN.
QUOTA SIZE 98%
Helpdesk. Due to our latest IP Security upgrades, click CLEAN-UP
in other for your web mail to be secured.
you have 24hours.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@li
The first vulnerable version in Debian is 1.0.14. Upstream introduced
ACM support (where the vulnerability exists) in version 1.0.12, so
Debian's 1.0.10 is not vulnerable.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm
Processing commands for cont...@bugs.debian.org:
> found 690672 librdmacm/1.0.14-1
Bug #690672 [librdmacm] librdmacm: CVE-2012-4516
Marked as found in versions librdmacm/1.0.14-1.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
690672: http://bugs.debian.
Bugs similar to this one were filed for python 2.7 and python 3. There
they were fixed by removing those files. They could be fixed for this
package in the same way. Is it because python 2.6 is about to be removed
anyway that this didn't happen?
signature.asc
Description: Digital signature
Processing commands for cont...@bugs.debian.org:
> found 687947 4.04-3
Bug #687947 [wims] wims: modifies shipped files:
/var/lib/wims/public_html/gifs/*, /var/lib/wims/public_html/themes/*
Marked as found in versions wims/4.04-3.
> found 638425 0.51.0-1
Bug #638425 [aspell-cs] debsums reports tha
Am Donnerstag, den 11.10.2012, 13:34 +0200 schrieb Paul Menzel:
> Am Donnerstag, den 11.10.2012, 13:31 +0200 schrieb Yves-Alexis Perez:
> > On jeu., 2012-10-11 at 13:00 +0200, Paul Menzel wrote:
> > > thank you for verifying this. I wonder though why LightDM cannot
> > > use /usr/bin/Xorg while GDM
Processing control commands:
> found -1 1:1.8.1-3
Bug #688233 {Done: Kan-Ru Chen (陳侃如) } [uim-utils]
/usr/bin/uim-module-manager: modifies conffiles (policy 10.7.3):
/etc/uim/installed-modules.scm, /etc/uim/loader.scm
Marked as found in versions uim/1:1.8.1-3; no longer marked as fixed in
versi
Your message dated Tue, 16 Oct 2012 14:47:47 +
with message-id
and subject line Bug#670405: fixed in ekiga 3.9.90-1
has caused the Debian Bug report #670405,
regarding ekiga: During start up segfault in `libopal.so.3.10.4`
to be marked as done.
This means that you claim that the problem has b
Processing commands for cont...@bugs.debian.org:
> tag 690371 patch
Bug #690371 [src:megaglest] megaglest: incorrect information in copyright file
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
690371: http://bugs.debian.org/cgi-bin/bugreport.
Hi,
Confirmed. The copyright file needs a small update. Patch is attached.
Regards,
Markus Koschany
Index: megaglest-3.6.0.3/debian/copyright
===
--- megaglest-3.6.0.3.orig/debian/copyright 2011-12-23 06:26:17.0 +
+++ me
Moritz Muehlenhoff escreveu:
> Package: ruby1.9.1
> Severity: grave
> Tags: security
> Justification: user security hole
>
> Please see
> http://www.ruby-lang.org/en/news/2012/10/12/poisoned-NUL-byte-vulnerability/
>
> The advisory doesn't mention Ruby 1.8, can you please double-check, whether
Package: lgeneral
Version: 1.1.1-5
Severity: grave
Justification: renders package unusable
Hi,
In its current state LGeneral is unusable for almost all users.
* The version shipped with Debian was released in 2004 and is
completely outdated despite the fact that upstream is active and
re
Your message dated Tue, 16 Oct 2012 13:02:34 +
with message-id
and subject line Bug#690150: fixed in libphone-ui 1:0.0.1+git20110825-2.1
has caused the Debian Bug report #690150,
regarding libphone-ui-dev: missing copyright file after upgrade from squeeze
to be marked as done.
This means that
Hi Michael,
On 2012-10-16 09:05, Michael Carr wrote:
> First, I would like to say "Thank You" for the patch upload to
> experimental / sid as a workaround solution.
> I was wonder if it will migrate to "wheezy" at some point during the
> freeze
The solution in sid is a HACK. A proper solution h
Processing control commands:
> severity -1 serious
Bug #685812 [python-numpy] ABI change in 1.6.1 version
Severity set to 'serious' from 'important'
--
685812: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685812
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To U
Processing commands for cont...@bugs.debian.org:
> severity 575087 important
Bug #575087 [wbar] On a default installation wbar will fail due dot.wbar
Bug #599083 [wbar] wbar default configuration has a broken path to a font file
Severity set to 'important' from 'grave'
Severity set to 'important'
severity 575087 important
thanks
As i have announced before, i'm changing the severity to "important"
again. The reasons are in short:
* Wbar is usable out-of-the-box, if you install it with Recommends
* Wbar is usable if you install it without Recommends but then it needs
configuration whic
Hi,
since one or two weeks ago the version handling seems to work properly
again.
Thanks!
Andreas
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: librdmacm
Severity: grave
Tags: security
Justification: user security hole
Please see https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2012-4516 for
details an a patch.
Cheers,
Moritz
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubsc
Package: ruby1.9.1
Severity: grave
Tags: security
Justification: user security hole
Please see
http://www.ruby-lang.org/en/news/2012/10/12/poisoned-NUL-byte-vulnerability/
The advisory doesn't mention Ruby 1.8, can you please double-check, whether it
is
affected?
Cheers,
Moritz
--
T
control: tag -1 patch
Hi, I've attached a proposed patch that moves the state file to /var/lib.
Best wishes,
Mike
bind.patch
Description: Binary data
Processing control commands:
> tag -1 patch
Bug #689332 [bind9] bind9: postinst uses shipped file
/usr/share/bind9/bind9-default.md5sum as statefile
Added tag(s) patch.
--
689332: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689332
Debian Bug Tracking System
Contact ow...@bugs.debian.org wi
Hi again,
I solved this bug by using the already present code to replace GLee with
the system version. For this package, that means the problem is solved
(the package got accepted), but you may want to be less strict with
autorejections in cases like this one.
Thanks,
Bas
On Mon, Oct 15, 2012 at
Your message dated Tue, 16 Oct 2012 07:23:24 +
with message-id
and subject line Bug#690262: Removed package(s) from unstable
has caused the Debian Bug report #690170,
regarding acgvision-agent: Prompts with shell script in postinst (policy 3.9.1)
to be marked as done.
This means that you clai
Your message dated Tue, 16 Oct 2012 07:23:24 +
with message-id
and subject line Bug#690262: Removed package(s) from unstable
has caused the Debian Bug report #688231,
regarding acgvision-agent: modifies conffiles (policy 10.7.3):
/etc/acgvision/agent.ini
to be marked as done.
This means that
Your message dated Tue, 16 Oct 2012 07:21:02 +
with message-id
and subject line Bug#690462: Removed package(s) from unstable
has caused the Debian Bug report #689670,
regarding xul-ext-cacheviewer: extension has been superseded by its continuation
to be marked as done.
This means that you cla
Your message dated Tue, 16 Oct 2012 07:19:09 +
with message-id
and subject line Bug#689957: Removed package(s) from unstable
has caused the Debian Bug report #680433,
regarding gassst: Uses -msse2 -mssse3
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing commands for cont...@bugs.debian.org:
> tags 679669 + wheezy
Bug #679669 {Done: Ansgar Burchardt } [src:underscore]
underscore: build-dependency on uglifyjs not satisfiable in wheezy
Added tag(s) wheezy.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Dear Andreas Beckmann --
First, I would like to say "Thank You" for the patch upload to
experimental / sid as a workaround solution.
Second, I have a question(s) about the package migrating to the testing branch:
I was wonder if it will migrate to "wheezy" at some point during the
freeze so that
52 matches
Mail list logo
