On Tue, 02 Jun 2009, Alban Browaeys wrote:
> And there seems to be a bug in the mv_db is triggers:
> [ -e /var/lib/mediatomb/sqlite3.db ] && \
> cp --preserve /var/lib/mediatomb/sqlite3.db
> /var/lib/mediatomb/mediatomb.db
> alsways returns 1 which errors out the postinst. Adding
> "|| r
Processing commands for cont...@bugs.debian.org:
> tags 521185 - sid
Bug#521185: libmyodbc: Creashes with symbol error
Tags were: sid patch
Bug#522968: myodbc: FTBFS: libmyodbc3_r.so: undefined reference to
`mysql_odbc_escape_string'
Bug#523593: myodbc_3.51.15r409-4+b1(mips/unstable): FTBFS on mi
Le Sun, Jun 14, 2009 at 10:33:03PM +, Debian Bug Tracking System a écrit :
> > severity 523715 serious
Hello Moritz, Steffen and Philipp,
I will upload soon an update with Barry's patch.
Have a nice day,
--
Charles Plessy
Debian Med packaging team,
http://www.debian.org/devel/debian-med
Ts
Your message dated Mon, 15 Jun 2009 04:32:13 +
with message-id
and subject line Bug#529023: fixed in torcs 1.3.1-2
has caused the Debian Bug report #529023,
regarding torcs: FTBFS: libtoolize: command not found
to be marked as done.
This means that you claim that the problem has been dealt w
Your message dated Mon, 15 Jun 2009 03:18:40 +
with message-id
and subject line Bug#528635: fixed in flightgear 1.9.1-1
has caused the Debian Bug report #528635,
regarding depends on plib1.8.4c2 which is unavailable
to be marked as done.
This means that you claim that the problem has been de
Package: gliv
Version: 1.9.5-1
Severity: grave
Justification: renders package unusable
Immediate segfault with error message:
(gliv:6112): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion
`atom != GDK_NONE' failed
-- System Information:
Debian Release: squeeze/sid
APT prefers unsta
Package: sitecopy
Severity: normal
Yes, the version number was mine, I used checkinstall. The installed sources
were of version 0.16.6-2.
I am new to reportbug and I didn't do anything to suppress dependency
information.
To fix, added entries for unstable in my /etc/apt/sources.list file.
Then
Package: sitecopy
Severity: normal
Hi Sandro !
* The version was created while using checkinstall, so the extra numbering is
mine.
* apt-get source retrieved the following files :
sitecopy_0.16.6-2.diff.gz, sitecopy_0.16.6-2.dsc
So I assumed this would be for a 0.16.6-2 version
* I'll try to
Package: ruby1.8-dev
Version: 1.8.7.72-3.1
Severity: serious
Hi, I maintain a package with Swig-generated interfaces for which I also
provide ruby builds. I had just done a release a few days ago, it worked
fine:
dh_installdirs -pquantlib-ruby usr/share/quantlib-ruby
(cd Ruby &&
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
On Sun, Jun 14, 2009 at 07:36:32PM +0800, Fabrice Colin wrote:
>On Sat, Jun 13, 2009 at 11:57 PM, Jonas Smedegaard wrote:
>> Unfortunately my first attempt didn't work out as intended.
>>
>> Haven't found time to verify yet, but seems to be that I
Your message dated Sun, 14 Jun 2009 21:34:35 +
with message-id
and subject line Bug#527518: fixed in umview 0.6-1
has caused the Debian Bug report #527518,
regarding umview: FTBFS: Cannot find linux/dirent.h
to be marked as done.
This means that you claim that the problem has been dealt with
On Fri, Jun 12, 2009 at 09:50:22PM -0700, Cameron Dale wrote:
> On Tue, Jun 2, 2009 at 11:45 AM, Moritz Muehlenhoff wrote:
> > The following security issues have been reported against torrentflux:
> >
> > http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-6584
> > http://cve.mitre.org/cgi-bin/c
Your message dated Sun, 14 Jun 2009 21:33:17 +
with message-id
and subject line Bug#530470: fixed in licq 1.3.6-2
has caused the Debian Bug report #530470,
regarding Fails to build -- attempts to access file in /usr/share/icons
to be marked as done.
This means that you claim that the problem
Hi
pythonmagick is blocking the imagemagick transition (and some
transitions waiting for this to finish). I heard from Bernd (bzed) that
uploading the new upstream version to fix the outstanding RC bugs still
needs some work (patching to get it build with python2.5?).
So I wanted to request if re
* Rafael Laboissiere [2009-06-14 15:39]:
> * Rafael Laboissiere [2009-06-14 12:25]:
>
> > I think that the different values of x_max and x_min explain the bug on
> > the mips system. I guess that this is caused by the following lines in
> > pr-output.cc (function set_format):
> >
> > in
On Sat, Jun 13, 2009 at 10:43:55PM +0300, Niko Tyni wrote:
> Security team: I'm attaching proposed debdiffs for stable updates.
> Do you agree that this fix is sufficient? Shall I go ahead and upload?
Update: I've got confirmation from upstream that the one line fix should be
fine. Just say the
Processing commands for cont...@bugs.debian.org:
> # Sun Jun 14 20:04:47 UTC 2009
> # Tagging as pending bugs that are closed by packages in NEW
> # http://ftp-master.debian.org/new.html
> #
> # Source package in NEW: gfm
> tags 532606 + pending
Bug#532606: ITP: gfm -- Texas Instruments hand-helds
Package: gnome-python-desktop
Version: 2.24.1-1+b3
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of gnome-python-desktop_2.24.1-1+b3 on mayr by sbuild/mips
> 99.999
> Build started at 20090612-1233
[...]
> ** Using build dependencies supplied by
Your message dated Sun, 14 Jun 2009 16:47:10 +
with message-id
and subject line Bug#527065: fixed in util-vserver 0.30.216~r2772-7
has caused the Debian Bug report #527065,
regarding owned and unowned files after purge (policy 6.8 + 10.7.3)
to be marked as done.
This means that you claim tha
* Andrew Lee [2009-06-14 12:57-0400]:
> Hi Micah,
>
> Micah Anderson wrote:
> > Hi Andrew,
> > I appreciate the help with the package, although typically a NMU is done
> > after a patch is not being applied, so sending a patch and doing a 2-day
> > NMU at the same time is a little aggressive. I'm
Hi Micah,
Micah Anderson wrote:
> Hi Andrew,
> I appreciate the help with the package, although typically a NMU is done
> after a patch is not being applied, so sending a patch and doing a 2-day
> NMU at the same time is a little aggressive. I'm also wondering how you
> can do this NMU because as
On Sat, Jun 13, 2009 at 08:32:17PM +0200, Hadmut Danisch wrote:
>
> running sympa or sympa perl scripts, e.g.
> /etc/init.d/sympa start
> or the sympa.pl reports
>
> $* is no longer supported at /usr/lib/sympa/bin/parser.pl line 65.
>
>
> looks as if sympa is not compatible with latest perl ve
Your message dated Sun, 14 Jun 2009 15:39:51 +
with message-id
and subject line Bug#529783: fixed in rt-tests 0.39-2
has caused the Debian Bug report #529783,
regarding rt-tests and xenomai-runtime: error when trying to install together
to be marked as done.
This means that you claim that th
On Sun, Jun 14, 2009 at 05:10:46PM +0200, Manuel Prinz wrote:
> Hi everyone!
>
> On Fri, June 12, 2009 11:10 pm, Jeff Squyres wrote:
> > Agreed. We thought that stat() was safe to call in the malloc init
> > hook -- it seems to be in most other places, at least.
Jeff, I agree that one would expe
Hi Andrew,
* Andrew Lee [2009-06-13 02:40-0400]:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> tags 527065 +patch
> thanks
>
> Dear maintainer,
>
> I've prepared an NMU for util-vserver (versioned as 0.30.216~r2772-6.1).
> And it will be uploaded to DELAYED/02. Please free to tell me
Ritesh,
// also CC-ed Tetsuo Handa, he is main developer of TOMOYO Linux.
Maybe, ccs-auditd is not related ccs-editpolicy problem.
Please Try;
# /usr/lib/ccs/tomoyo_init_policy.sh
in your TOMOYO enabled environemnts, and reboot it.
You can use ccs-editpolicy commands... could you?
// That is heur
Hi everyone!
On Fri, June 12, 2009 11:10 pm, Jeff Squyres wrote:
> Agreed. We thought that stat() was safe to call in the malloc init
> hook -- it seems to be in most other places, at least.
>
> If there's some other safe way to check that stat() is *not* safe,
> that would be great.
Unfortunate
Hito,
I see a lot of these messages in syslogd.
Jun 13 23:35:10 learner ccs-auditd: Can't open
/sys/kernel/security/tomoyo/grant_log for reading.
Jun 13 23:37:03 learner ccs-auditd: Can't open
/sys/kernel/security/tomoyo/grant_log for reading.
Jun 13 23:37:25 learner ccs-auditd: Can't open
/sy
Hi Hito,
On Sunday 14 Jun 2009 19:31:16 h...@kugutsu.org wrote:
> Hi Ritesh,
>
> Did you set security=tomoyo to your kernel boot args?
>
> In 2.6.30s TOMOYO Linux (TOMOYO 2.x, a.k.a LSM version), that is LSM
> implementations.
>
Yes. I did add security=tomoyo in the kernel command line. The same
Your message dated Sun, 14 Jun 2009 10:49:06 -0400
with message-id <4a350de2.5090...@debian.org>
and subject line Re: Bug#533033: gcc-4.4: gcc and g++ do not find their cc1 and
cc1plus binaries
has caused the Debian Bug report #533033,
regarding gcc-4.4: gcc and g++ do not find their cc1 and cc1p
Processing commands for cont...@bugs.debian.org:
> found 521373 0.2.27-1
Bug#521373: gimageview: Opening preferences causes segfault
Bug marked as found in version 0.2.27-1.
> fixed 521373 0.2.27-2
Bug#521373: gimageview: Opening preferences causes segfault
Bug marked as fixed in version 0.2.27-2
Your message dated Sun, 14 Jun 2009 13:45:09 +
with message-id
and subject line Bug#521553: fixed in linux-2.6 2.6.30-1
has caused the Debian Bug report #521553,
regarding Staging drivers contain non-free firmware
to be marked as done.
This means that you claim that the problem has been deal
Hi Ritesh,
Did you set security=tomoyo to your kernel boot args?
In 2.6.30s TOMOYO Linux (TOMOYO 2.x, a.k.a LSM version), that is LSM
implementations.
Default LSM modules are SELinux, we must set activate LSM mods in kopts.
Regards,
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.d
* Rafael Laboissiere [2009-06-14 12:25]:
> I think that the different values of x_max and x_min explain the bug on
> the mips system. I guess that this is caused by the following lines in
> pr-output.cc (function set_format):
>
> int x_max = max_abs == 0.0
On Sat, Jun 13, 2009 at 11:57 PM, Jonas Smedegaard wrote:
> Unfortunately my first attempt didn't work out as intended.
>
> Haven't found time to verify yet, but seems to be that I should set
> CPPFLAGS instead of CFLAGS (they are handled separately in CDBS
> packaging tool).
>
> Perhaps your upstr
Package: python-kde3
Version: 3.16.1-1
Severity: serious
Python programs segfault when import dcopext module.
$ python2.5
Python 2.5.4 (r254:67916, Feb 17 2009, 20:16:45)
[GCC 4.3.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import dcopext
zsh: segmenta
* Rafael Laboissiere [2009-06-13 09:15]:
> So, even if log2 returns a wrong value, the bug happens elsewhere. At any
> rate, the following works as expected:
>
> complex (NaN, NaN)
> complex (0, NaN)
> complex (NaN, Inf)
>
> I am puzzled with this problem and I cannot really debug i
Processing commands for cont...@bugs.debian.org:
> # Automatically generated email from bts, devscripts version 2.10.35lenny3
> tags 521553 + pending
Bug#521553: Staging drivers contain non-free firmware
Tags were: pending
Tags added: pending
>
End of message, stopping processing here.
Please co
38 matches
Mail list logo
