Package: gnomemeeting
Version: 1.2.3-5
Severity: serious
Tags: patch
When building 'gnomemeeting' in a clean 'unstable' chroot,
I get the following error:
checking for EDS_LIBS...
checking for EDS_CFLAGS...
checking for EDS_LIBS...
configure: error: Package requirements (libebook-1.0 >= 0.0.94
Your message dated Mon, 14 Aug 2006 23:02:10 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#383101: fixed in policycoreutils 1.30.26-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
On Mon, Aug 14, 2006 at 08:15:23PM -0400, sean finney wrote:
> i think we'll have to go for the latter. there was a similar problem
> a while back when there was stuff i needed to do in the prerm script,
^^^preinst
sean
signatu
Your message dated Mon, 14 Aug 2006 22:02:19 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#379720: fixed in linux-kernel-headers 2.6.17.8-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the c
Processing commands for [EMAIL PROTECTED]:
> retitle 382561 Uninstallable due to unmet dep on bzr (<< 0.9)
Bug#382561: bzrtools: New upstream release
Changed Bug title.
> severity 382561 serious
Bug#382561: Uninstallable due to unmet dep on bzr (<< 0.9)
Severity set to `serious' from `wishlist'
Your message dated Mon, 14 Aug 2006 21:02:20 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#380845: fixed in hplip 1.6.7-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Processing commands for [EMAIL PROTECTED]:
> package qpopper
Ignoring bugs not assigned to: qpopper
> close 330123
Bug#330123: qpopper: poppassd local root exploit?
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug closed, send any further explanations to Martin Pitt <[
tags 382783 pending
thanks
I've reviewed the NMU prepared by Arjan, built it and tested it. It fixes
the problem and it's a very simple fix.
Therefore, I intend to upload it as an NMU.
The patch is exactly the same submitted by Arjan. Clean and simple.
Since this bug has just been reported, I'
Processing commands for [EMAIL PROTECTED]:
> tags 382783 pending
Bug#382783: yacas: None of the most basic examples work
Tags were: patch
Tags added: pending
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Deb
Package: boson
Version: 0.11-4
Severity: grave
Justification: renders package unusable
i installed package on 2 debian sid systems:
one is smp k7 one is ibook g4 notebook.
on both systems on starting program and invoking single user mode i get kde
crash window with this output from console
[EM
Package: policycoreutils
Version: 1.30.26-1
Severity: grave
Justification: renders package unusable
semanage doesn't work:
/usr/sbin/semanage
Traceback (most recent call last):
File "/usr/sbin/semanage", line 24, in ?
import seobject
ImportError: No module named seobject
The file
/usr/sha
After a request from a release manager on IRC and as the BR is over a week
old, I have uploaded and NMU with the suggested patch.
Only changes:
- Changed version number for NMU
- Indicated NMU in changelog
Cheers,
FJP
pgp07Lt8SJkBa.pgp
Description: PGP signature
On Mon, Aug 14, 2006 at 08:15:23PM -0400, sean finney wrote:
> > Admittedly, this is a policy violation that bacula doesn't have compliant
> > postrm scripts, but I'm not sure that it's a problem with dbconfig-common.
>
> yes, bacula is not policy complaint as reported in the bug logs, but
> i'll
Processing commands for [EMAIL PROTECTED]:
> severity 383098 normal
Bug#383098: Installing zope-common attempts to remove kernel-image-2.6.8-2-386
Severity set to `normal' from `critical'
> tags 383098 + unreproducible
Bug#383098: Installing zope-common attempts to remove kernel-image-2.6.8-2-386
Package: smart-notifier
Version: 0.27-1
Severity: serious
Justification: fails to install
Setting up smart-notifier (0.27-1) ...
Stopping Avahi mDNS/DNS-SD Daemon: avahi-daemon.
Stopping Hardware abstraction layer: hald.
Stopping system message bus: dbus.
Starting system message bus: dbus.
Startin
severity 383098 normal
tags 383098 + unreproducible
thanks
Mark Phillips writes:
> Package: zope-common
> Severity: critical
> Justification: breaks the whole system
>
> Running 'apt-get -t testing install zope-common' reported that my
> kernel-image had to be removed. This does not happen when I
Alexander Sack a écrit :
Why seamonkey has been rejected? I would really be curious about that
info. A packaging issue? I hope it was not a "licensing issue".
http://www.braincells.com/debian/index.cgi/search/item=146
Why seamonkey has been rejected? I would really be curious about that
info. A packaging issue? I hope it was not a "licensing issue".
- Alexander
--
GPG messages preferred. | .''`. ** Debian GNU/Linux **
Alexander Sack| : :' : The universal
[EMAIL PROTECTED]
Package: zope-common
Severity: critical
Justification: breaks the whole system
Running 'apt-get -t testing install zope-common' reported that my
kernel-image had to be removed. This does not happen when I try to
install other packages (like zope2.8). This is the only kernel-image I
have running on
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.20
> # renders package unusable on amd64
> severity 382429 grave
Bug#382429: samba: problem detecting network interfaces
Severity set to `grave' from `normal'
>
End of message, stopping
On Tue, 15 Aug 2006, Alexander Sack wrote:
Why seamonkey has been rejected? I would really be curious about that
info. A packaging issue? I hope it was not a "licensing issue".
No it was packaging issues. Three pages worth of lintian errors!
--
Jaldhar H. Vyas <[EMAIL PROTECTED]>
La Salle
hey john, stephen,
On Tue, Aug 15, 2006 at 12:17:05AM +0100, Stephen Gran wrote:
> The problem is needing a non-essential package during purge. This means
> one of two things: dbconfig-common becomes essential (not that great,
> IMHO - it's big enough already), or the rest of the world that relie
reassign 382956 ftp.debian.org
retitle 382956 RM: mozilla -- unmaintained, dead upstream, RC-buggy
reassign 370436 ftp.debian.org
forcemerge 382956 370436
thanks
Alexander Sack - Debian Bugmail a écrit :
On Mon, Aug 14, 2006 at 06:34:24AM -0400, Filipus Klutiero wrote:
Package: mozilla
Seve
Aurelien Jarno a écrit :
On Mon, Aug 14, 2006 at 01:37:46AM -0400, Filipus Klutiero wrote:
Package: mozilla-locale-fr
Severity: serious
mozilla-locale-fr depends on mozilla-browser, which is scheduled to be
removed from Etch. You should most likely request removal from
ftp-master.
Y
Processing commands for [EMAIL PROTECTED]:
> retitle 380706 RM: spca5xx-modules-i386 -- RoM; superseded by
> spca5xx-modules, RC-buggy
Bug#380706: RM: spca5xx-modules-i386 -- RoM; superseded by spca5xx-modules
Changed Bug title.
> severity 380706 grave
Bug#380706: RM: spca5xx-modules-i386 -- RoM
Processing commands for [EMAIL PROTECTED]:
> severity 376428 grave
Bug#376428: Uninstallable due to dep on linux-image-2.6.16-1-*
Severity set to `grave' from `serious'
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
tag 382783 patch
thanks
Hi,
As I had prepared the patch for the previous NMU I have prepared a new
patch which fixes the runtime issues due to the underexpanded variables.
Marga, as you did the previous NMU, I guess you don not mind doing
another NMU on yacas?
Greetings Arjan
diff -u yacas
Processing commands for [EMAIL PROTECTED]:
> reassign 382956 ftp.debian.org
Bug#382956: mozilla: Shipping secure Mozilla in Etch would require unreasonable
maintainance
Bug reassigned from package `mozilla' to `ftp.debian.org'.
> retitle 382956 RM: mozilla -- unmaintained, dead upstream, RC-bugg
Processing commands for [EMAIL PROTECTED]:
> tag 382783 patch
Bug#382783: yacas: None of the most basic examples work
There were no tags set.
Tags added: patch
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, D
Package: plone-site
Version: 2.5-1
Severity: grave
Justification: renders package unusable
I am running Debian testing on i386. I just upgraded to plone-site 2.5-1 and
Zope 2.9. I was running the previous release on Plone on Zope 2.8. After
the upgrade Plone would not work on Zope 2.8 or Zop
On Mon, 2006-08-14 at 04:45 -0400, Filipus Klutiero wrote:
> Oops, I obviously sent this a little too fast. In this case there's
> probably a way to let the package depend on alternatives.
It already does.
--
David Moreno Garza<[EMAIL PROTECTED]>
http://www.damo
Your message dated Mon, 14 Aug 2006 15:47:12 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#382012: fixed in apt-proxy 1.9.35
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now y
This one time, at band camp, John Goerzen said:
> I am following the design set forth in the dbconfig-common docs and
> examples. You appear to be referencing section 7.2 of policy.
>
> I am reassinging this to dbconfig-common since I can't do anything about
> it if dbconfig-common requires packa
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.20
> forwarded 382250 http://www.cups.org/espgs/str.php?L1911
Bug#382250: gs-esp doesn't print german umlauts
Noted your statement that Bug has been forwarded to
http://www.cups.org/espgs
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.20
> merge 381386 382250
Bug#381386: gs-esp: doesn't render accents in accented polish letters using
truetype fonts
Bug#382250: gs-esp doesn't print german umlauts
Merged 381386 382250.
Package: plone-site
Version: 2.5-1
Severity: grave
Justification: renders package unusable
I am running Debian testing on i386. I just upgraded to plone-site 2.5-1 and
Zope 2.9. I was running the previous release on Plone on
Zope 2.8. After the upgrade Plone would not work on Zope 2.8 or Zop
Your message dated Mon, 14 Aug 2006 14:19:58 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#383044: fixed in xmms 1:1.2.10+20060801-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Your message dated Mon, 14 Aug 2006 14:19:58 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#380115: fixed in xmms 1:1.2.10+20060801-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Your message dated Mon, 14 Aug 2006 14:19:58 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#380321: fixed in xmms 1:1.2.10+20060801-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Your message dated Mon, 14 Aug 2006 14:19:30 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#381317: fixed in tightvnc 1.2.9-19
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Mon, 14 Aug 2006 14:19:58 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#380115: fixed in xmms 1:1.2.10+20060801-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Your message dated Mon, 14 Aug 2006 14:19:58 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#380318: fixed in xmms 1:1.2.10+20060801-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Your message dated Mon, 14 Aug 2006 15:02:28 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#383024: fixed in reportbug 3.25
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now you
Your message dated Mon, 14 Aug 2006 14:19:58 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#380318: fixed in xmms 1:1.2.10+20060801-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Your message dated Mon, 14 Aug 2006 14:19:58 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#380318: fixed in xmms 1:1.2.10+20060801-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Your message dated Mon, 14 Aug 2006 14:19:58 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#380321: fixed in xmms 1:1.2.10+20060801-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Your message dated Mon, 14 Aug 2006 14:19:58 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#380321: fixed in xmms 1:1.2.10+20060801-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Your message dated Mon, 14 Aug 2006 14:19:58 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#380115: fixed in xmms 1:1.2.10+20060801-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Processing commands for [EMAIL PROTECTED]:
> reassign 379720 linux-kernel-headers
Bug#379720: vdr-plugin-bitstreamout: FTBFS: error: 'fls' was not declared in
this scope
Bug reassigned from package `vdr-plugin-bitstreamout' to `linux-kernel-headers'.
> tags 379720 patch
Bug#379720: vdr-plugin-bi
reassign 379720 linux-kernel-headers
tags 379720 patch
I am reassigning this bug to linux-kernel-headers as it seems to be the root
cause for this FTBFS, the last upload of vdr-plugin-bitstreamout was in on
2006-04-30, at this time it was built without any problems. A few tests
showed that this
On Mon, 2006-08-14 at 09:33 +0100, Sam Clegg wrote:
> Well, to be honest, I only switched to gmcs (and therefore 2.0)
> because it seemed to be the default way for nant to build boo.
CLR 2.0 is still far from stable and is not officially supported
upstream, it's work in progress.
Even Mono 1.2 wi
found 361853 4:4.4.2-1.1
thanks
according to secunia [1], this has been fixed in 4.4.3, not in 4.4.2
[1] http://secunia.com/advisories/19599
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[Peter Eisentraut]
> I will upload an NMU based on the attached patch in a few days if
> the bug is not addressed by then.
Good to hear, as this bug make it impossible for the ntp package to
propage into etch, and radioclk is impossible to install in unstable:
# aptitude install radioclk
Reading
Processing commands for [EMAIL PROTECTED]:
> found 361853 4:4.4.2-1.1
Bug#361853: [CVE-2006-0996] phpinfo() Cross Site Scripting
Bug marked as found in version 4:4.4.2-1.1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(adm
Processing commands for [EMAIL PROTECTED]:
> reassign 383063 dbconfig-common
Bug#383063: Uses non-Essential: yes packages in postrm purge & abort-
Bug reassigned from package `bacula-director-pgsql' to `dbconfig-common'.
> thanks
Stopping processing here.
Please contact me if you need assistance
reassign 383063 dbconfig-common
thanks
I am following the design set forth in the dbconfig-common docs and
examples. You appear to be referencing section 7.2 of policy.
I am reassinging this to dbconfig-common since I can't do anything about
it if dbconfig-common requires packages to act this wa
On Mon, 2006-08-14 at 22:06 +0200, Andrea Borgia wrote:
> > I think the best thing to do is to stop interfering with
> > jabber/jabber-common, and create a separate user to run pymsnt.
>
> A separate unprivileged user might be a good idea anyway, but I am
> unsure how that would help with respect
On Mon, Aug 14, 2006 at 02:07:48PM +0400, Nikita V. Youshchenko wrote:
> > Processing commands for [EMAIL PROTECTED]:
> > > # Automatically generated email from bts, devscripts version 2.9.20
> > > found 375611 0.45-3
> > Bug#375611: libetpan: FTBFS/ia64
> > Bug marked as found in version 0.45-3.
Processing commands for [EMAIL PROTECTED]:
> retitle 382861 Please allow update from Sarge's teTeX
Bug#382861: installing texlive over tetex fails
Changed Bug title.
> severity 382861 normal
Bug#382861: Please allow update from Sarge's teTeX
Severity set to `normal' from `grave'
> thanks
Stoppin
Sam Morris wrote:
> I think the best thing to do is to stop interfering with
> jabber/jabber-common, and create a separate user to run pymsnt.
A separate unprivileged user might be a good idea anyway, but I am
unsure how that would help with respect to the log issue.
I see two possible solutio
severity 382752 normal
thanks
On Mon, Aug 14, 2006 at 17:58 +0800, LI Daobing wrote:
> On 8/14/06, Ralf Stubner <[EMAIL PROTECTED]> wrote:
> >On Sun, Aug 13, 2006 at 13:18 +0800, LI Daobing wrote:
> >> Package: texlive-base-bin
> >> Version: 2005.dfsg.1-1
> >> Severity: grave
> >> Justification: r
Processing commands for [EMAIL PROTECTED]:
> severity 382752 normal
Bug#382752: texlive-base-bin: can's install
Severity set to `normal' from `grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs
retitle 382861 Please allow update from Sarge's teTeX
severity 382861 normal
thanks
On Mon, Aug 14, 2006 at 14:38 +0400, Stanislav Maslovski wrote:
> On Mon, Aug 14, 2006 at 12:10:59PM +0200, Ralf Stubner wrote:
> [ ... ]
> > > Another thing that can be useful is that the version of tetex I had
>
Package: bacula-director-pgsql
Version: 1.38.11-2
Severity: serious
(Also in -1, and no doubt many previous versions)
The postrm script always uses dbconfig-common. Even if the first
parameter is 'purge' (policy says you may only use Essential: yes
packages in that case). Similarly, you can't use
Your message dated Mon, 14 Aug 2006 12:15:07 -0700
with message-id <[EMAIL PROTECTED]>
has caused the Debian Bug report #383052,
regarding python-libgmail: unable to log in
to be marked as having been forwarded to the upstream software
author(s) [EMAIL PROTECTED]
(NB: If you are a system administr
Processing commands for [EMAIL PROTECTED]:
> tag 383052 + confirmed upstream
Bug#383052: python-libgmail: unable to log in
There were no tags set.
Tags added: confirmed, upstream
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrato
tag 383052 + confirmed upstream
thanks
Hi dear libgmail maintainers,
I can reproduce this one too, have you heard about it at all ? :)
Sorry for the very short mail, I'm on vacation with only dialup access
right now...
Cheers,
--Seb
On Mon, Aug 14, 2006 at 08:45:34PM +0200, Jakub Wilk wrote:
On Mon, Aug 14, 2006 at 01:45:31PM +0200, Frans Pop wrote:
> On Monday 14 August 2006 10:18, Geert Stappers wrote:
> > [ this bug, severity 'grave', is blocking the release. ]
>
> No, but offering the option to users with the result that data on the
> partition will be destroyed (or at least unus
Your message dated Mon, 14 Aug 2006 14:31:09 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#382913: depends on mozilla
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your res
On Sun, 13 Aug 2006 03:44:32 +0200 Christian Surchi wrote:
> You are right, sorry.
> I saw old messages talking about a NMU, but it wasn't uploaded then,
> so I ACKed a not fixed package.
>
> Soon I'll upload new hasciicam, much better webcam support and no
> problem with GFDL.
Good, I'm lookin
severity 382985 important
tags 382985 wontfix
thanks
On Mon, Aug 14, 2006 at 04:16:06PM +0200, Adam Borowski wrote:
> A recently added optimization skips checksums on all packets it
> believes are destined for another Xen domain inside the same box.
> Too bad, it is sometimes wrong -- an analysis
Package: python-libgmail
Version: 0.1.4-3
Severity: grave
I am unable to log in:
$ python2.3 -c 'import libgmail; libgmail.GmailAccount("[EMAIL PROTECTED]",
"mySecretPassword").login()'
Traceback (most recent call last):
File "", line 1, in ?
File "/usr/lib/python2.3/site-packages/libgmail.py
Processing commands for [EMAIL PROTECTED]:
> block 370429 with 383040
Bug#370429: [tracker bug] Let's remove gnutls11 from sid/etch
Was blocked by: 335750 335752 335759 335764 335765 335771 370422 370423 370424
375206 378414
Blocking bugs of 370429 added: 383040
>
End of message, stopping proces
Processing commands for [EMAIL PROTECTED]:
> severity 382985 important
Bug#382985: teergrubes NATted connections due to mangled IPv4 checksums
Severity set to `important' from `grave'
> tags 382985 wontfix
Bug#382985: teergrubes NATted connections due to mangled IPv4 checksums
There were no tags
Package: amap
Version: 4.8-1.1
Severity: grave
Hi,
the amap package is uninstallable. When trying to install, postinst
always fails. The reason is, that it calls amap -W, which
automatically tries to update from www.thc.org:
% amap -W
Running Online Update for fingerprints, connecting to www.
Hi,
Attached is a better patch that fixes the build system to produce the
right jar.
James
--
James Westby --GPG Key ID: B577FE13-- http://jameswestby.net/
seccure key - (3+)k7|M*edCX/.A:n*N!>|&7U.L#9E)Tu)T0>AM - secp256r1/nistp256
diff -u commons-httpclient-3.0.1/debian/contr
Hi
I didn't fix Bug#379589 because rsjog can't work with
libgnome2-ruby (Bug#368513). I'm working on 368513, but I haven't the
Sony Notebook to test now, my new notebook is Thinkpad. So I'm not
sure whether it can be fixed.
Yu Guanghui
Processing commands for [EMAIL PROTECTED]:
> severity 382947 normal
Bug#382947: munin: Munin hangs on double cron-job execution and generates 100%
cpu load doing nothing
Severity set to `normal' from `grave'
> tags 382947 unreproducible
Bug#382947: munin: Munin hangs on double cron-job execution
Package: xmms
Version: 1:1.2.10+20060801-1
Severity: grave
Justification: renders package unusable
in this version of xmms only .a and .la files are distributed for most
xmms plugins. those plugins are not loaded by xmms,and are not
available. this also, but not only, includes alsa and oss output
Package: uim-applet-gnome
Version: 1:1.1.1-2
Severity: serious
uim-applet-gnome on i386 is linked against the obsolete libgnutls11.
The autobuilt versions are fine. libgnutls11 is dead upstream, won't
be part of etch, which is why I am choosing a serious severity.
Fixing this requires a source up
severity 382947 normal
tags 382947 unreproducible
quit
* Radek Antoniuk
> Now, the problem is that I have resolved the problem.. or maybe not
> the problem itself.
> I thought about the two cronjobs running simultaneously, and then... I
> thought, ok, let's try to restart crond. And it worked.
>
This was an error on my part during the last upload. Your patch looks
good, so I will apply it and look at getting it uploaded shortly.
Thanks,
James
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On 8/14/06, Tore Anderson <[EMAIL PROTECTED]> wrote:
Hmm. Could you next time take a look with "ps axuf", to see if
one is the child of the other?
Uhm, that was obvious and I've forgotten about it..
"Połączenie odrzucone" is "Connection refused ;))
Now, the problem is that I have resolved
> ==> munin-node.log <==
I assume "Nie ma takiego pliku ani katalogu" means "no such file or
directory", but I'll need help with "Połączenie odrzucone"... :-)
> It's totally repeatable. When I kill all pids of munin-*, and wait for
> next cronjob, it happens again.
Hmm. Could you change
package: libmusicbrainz-2.1
severity: grave
tags: security
Some buffer overflows have been found in libmusicbrainz up to 2.1.2.
See
http://aluigi.altervista.org/adv/brainzbof-adv.txt
http://secunia.com/advisories/21404/
for details.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subje
On Mon, Aug 14, 2006, Reuben Thomas wrote:
> In particular, I presume cooperation with upstream would expedite it? I
> for one am keen to see vlc in etch. I've written a note to upstream
> pointing out the problem a) in case they're not aware and b) to show
> that there are users who care.
>
>
Processing commands for [EMAIL PROTECTED]:
> severity 383018 important
Bug#383018: perl-tk crashes when creating new MainWindow
Severity set to `important' from `grave'
> tags 383018 unreproducible
Bug#383018: perl-tk crashes when creating new MainWindow
There were no tags set.
Tags added: unrepr
severity 383018 important
tags 383018 unreproducible
kthxbye
I'm unable to reproduce this issue. I'll ask on the perl-tk lists and
see if I can find a fix.
Michael Hartmann wrote:
> Package: perl-tk
> Version: 1:804.027-6
> Severity: grave
>
> A few days ago I've installed Debian testing on my
package: libmusicbrainz-2.0
severity: grave
tags: security
Some buffer overflows have been found in libmusicbrainz up to 2.1.2.
See
http://aluigi.altervista.org/adv/brainzbof-adv.txt
http://secunia.com/advisories/21404/
for details.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subje
Processing commands for [EMAIL PROTECTED]:
> tags 382322 = pending
Bug#382322: zeroc-ice-python: FTBFS: missing .so files
Tags were: patch
Tags set to: pending
> stop
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Deb
Your message dated Mon, 14 Aug 2006 09:32:04 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#375840: fixed in roundup 1.1.2-4
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Hi,
Thanks a lot.
I will fix another bugs soon as possible .
Regards,
Jose Carlos
2006/8/14, Thijs Kinkhorst <[EMAIL PROTECTED]>:
Hello,
I've fixed the bug (and added two debconf translations) in an NMU. The
final diff is attached. Hope this helps.
Thijs
--
[]'s
José Carlos
Package: reportbug
Version: 3.22
Severity: serious
Justification: Fails to install
Setting up reportbug (3.22) ...
/var/lib/dpkg/info/reportbug.postinst: line 27: /usr/bin/python2.3: No
such file or directory
So, use of python2.3 is hardcoded but reportbug depends only on current
version which is
Package: perl-tk
Version: 1:804.027-6
Severity: grave
A few days ago I've installed Debian testing on my computer and recognized
that perl-tk doesn't work. Everytime you try to create a new MainWindow it
aborts.
[EMAIL PROTECTED] /home/estel $ perl -MTk -we 'MainWindow->new'
8245384 is not a ha
Daniel Baumann wrote:
Kris Jurka wrote:
These can be fixed by adding
EGREP="grep -E"
max_cmd_len=32768
Thanks a lot, I applied a dpatch to fix it in ltmain.sh accordingly.
I doesn't look like the patch actually gets applied. debian/rules says:
configure: patch-stamp configure-stamp
confi
Processing commands for [EMAIL PROTECTED]:
> tag 379584 + fixed
Bug#379584: FTBFS: missing autoconf
Tags were: patch
Tags added: fixed
> tag 381383 + fixed
Bug#381383: [INTL:pt] Portuguese translation for webalizer (debconf)
Tags were: l10n patch
Tags added: fixed
> tag 382792 + fixed
Bug#382792
Hello,
I've fixed the bug (and added two debconf translations) in an NMU. The
final diff is attached. Hope this helps.
Thijs
diff -u webalizer-2.01.10/debian/changelog webalizer-2.01.10/debian/changelog
--- webalizer-2.01.10/debian/changelog
+++ webalizer-2.01.10/debian/changelog
@@ -1,3 +1,16 @
On Mon, Aug 14, 2006 at 04:03:31PM +0200, Jonas Smedegaard wrote:
> On Mon, 14 Aug 2006 14:57:21 +0200 Sven Luther wrote:
> > Jonas, i agree on this with maks and pierre, being able to override
> > root= is a very essential feature. Furthermore, it is not all that
> > difficult to implement (just c
On Mon, Aug 14, 2006 at 10:51:02AM +0200, Francisco Moya wrote:
> I sent the fixed package (along with some upstream patches) to my
> current package sponsor two days ago. I cannot sign them by myself. I
> sicerely hope you didn't actually issue an NMU as stated in the
> changelog.
I didn't, bec
Processing commands for [EMAIL PROTECTED]:
> severity 373963 grave
Bug#373963: drupal 4.5.8-1.1 filter.module is broken
Severity set to `grave' from `normal'
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administr
1 - 100 of 158 matches
Mail list logo
