Hi,
ntp 4.2.1rc1 was released in March (see
http://lists.ntp.isc.org/pipermail/announce/2006-March/12.html).
Looking through that, we see that:
1) The arlib/ stuff is still completely non-DFSG-free, and needs to be
ripped out of ntp. I'm open to any suggestions of async dns resolvers
that
Package: libjack0.100.0-0
Version: 0.101.1-1
Severity: grave
Justification: renders package unusable
08:41:45.373 jackd -v -R -dalsa -dhw:0 -r44100 -p2048 -n3 -S
08:41:45.379 JACK was started with PID=5754 (0x167a).
getting driver descriptor from /usr/lib/libjack0.100.0-0/jack_alsa.so
could not
Processing commands for [EMAIL PROTECTED]:
# Fixes were available in the pkg-gnome repository for a while...
tag 317924 pending
Bug#317924: gnome2-user-guide: Newer version available
There were no tags set.
Tags added: pending
tag 317926 pending
Bug#317926: gnome2-user-guide: Gnome2 user
Package: lastfm
Version: 1.1.90-3
Severity: grave
Justification: renders package unusable
I cannot start lastfm. It seems that there is a problem with libasound version:
lastfm: relocation error: lastfm: symbol snd_pcm_hw_params_get_channels_min,
version ALSA_0.9.0rc4 not defined in file
Downgrading libasound2 from 1.0.11-5 to 1.0.11-3 solved the problem for me.
Cheers,
Andreas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
The bug was reported for libasound2 as #369045. It is tagged as grave there.
Cheers,
Andreas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.19
reassign 369196 libasound2
Bug#369196: lastfm: Does not start - libasound version problem
Bug reassigned from package `lastfm' to `libasound2'.
merge 369050 369196
Bug#369050: bts:
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.19
reassign 369201 libasound2
Bug#369201: libjack0.100.0-0: symbol snd_pcm_hw_params_get_format not defined
with link time reference
Bug reassigned from package `libjack0.100.0-0' to
Package: udev
Version: 0.092-2
Severity: critical
Justification: breaks the whole system
Hi, ...
I tried a sarge to sid dist-upgrade on a powerpc/pegasos machine which was
running 2.6.8 kernel.
The upgrade failed with the udev needs kernel bigger than 2.6.12 message,
which was expected. But
Your message dated Sun, 28 May 2006 11:22:35 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#369207: sarge-sid dist-upgrade is impossible,
gnome/udev/kernel circular dep
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been
Your message dated Sun, 28 May 2006 11:40:37 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#368645: CVE-2006-2313, CVE-2006-2314: encoding conflicts
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
On Sun, May 28, 2006 at 11:22:35AM +0200, Marco d'Itri wrote:
On May 28, Sven Luther [EMAIL PROTECTED] wrote:
Now, i tried installing the linux-image package, but apt didn't let me do
this, because of the above installability problems, resulting in a broken
apt/dpkg database, and no easy
Processing commands for [EMAIL PROTECTED]:
# fixing typo
unmerge 369050
Bug#369050: bts: Add support for the forcemerge control command
Bug#369040: libasound2: 78 symbols have gone weak, making all linking apps break
Bug#369041: libasound2: Incompatibility with libesd-alsa0 0.2.36-3?
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.20
merge 369040 369196
Bug#369040: libasound2: 78 symbols have gone weak, making all linking apps break
Bug#369196: lastfm: Does not start - libasound version problem
Bug#369041:
Hi Kenshi,
Is there any progress on this bug? The cupsys packages have been out of
sync between testing and unstable for at least 5 months now, which means
amd64 has had no opportunity to get binaries of this package into etch. If
cupsys is going to be delayed much longer, we probably need to
Your message dated Sun, 28 May 2006 03:47:23 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#369040: fixed in alsa-lib 1.0.11-6
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 Sun, 28 May 2006 03:47:23 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#369040: fixed in alsa-lib 1.0.11-6
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 Sun, 28 May 2006 03:47:23 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#369040: fixed in alsa-lib 1.0.11-6
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 Sun, 28 May 2006 03:47:23 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#369040: fixed in alsa-lib 1.0.11-6
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 Sun, 28 May 2006 03:47:23 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#369040: fixed in alsa-lib 1.0.11-6
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 Sun, 28 May 2006 03:47:23 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#369040: fixed in alsa-lib 1.0.11-6
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 Sun, 28 May 2006 03:47:23 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#369040: fixed in alsa-lib 1.0.11-6
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 Sun, 28 May 2006 03:47:23 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#369040: fixed in alsa-lib 1.0.11-6
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 Sun, 28 May 2006 03:47:23 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#369040: fixed in alsa-lib 1.0.11-6
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 Sun, 28 May 2006 03:47:23 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#369040: fixed in alsa-lib 1.0.11-6
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 Sun, 28 May 2006 03:47:23 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#369040: fixed in alsa-lib 1.0.11-6
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 Sun, 28 May 2006 03:47:23 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#369040: fixed in alsa-lib 1.0.11-6
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 Sun, 28 May 2006 03:47:23 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#369040: fixed in alsa-lib 1.0.11-6
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 Sun, 28 May 2006 03:47:23 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#369040: fixed in alsa-lib 1.0.11-6
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
Hello
tag 357355 + fixed
Bug#357355: FTBS: fails to build for current unstable (duplicate template
instantiation)
Tags were: patch
Bug#360553: packagesearch_2.0.6(amd64/unstable): FTBFS: duplicate explicit
instantiation of 'class Tagcoll::OpSetint'
Tags added: fixed
You might have
tags 358289 + pending
tags 367045 + pending
thanks
I've uploaded the following NMU to delayed-3.
diff -u rezound-0.12.2beta/debian/changelog rezound-0.12.2beta/debian/changelog
--- rezound-0.12.2beta/debian/changelog
+++ rezound-0.12.2beta/debian/changelog
@@ -1,3 +1,14 @@
+rezound
Cedric Foll wrote:
Package: prelude-manager
Severity: grave
Justification: renders package unusable
The package libpreludedb0 doesn't seem available and is needed in order
to install the package prelude-manager.
I know about that. The package is in the new queue and is waiting for
Hi security team,
I backported the relevant changes from 7.4.13 and put the sarge
security update to [1]. This time, just putting 7.4.13 into
sarge-security would even have been safer IMHO, and that's what users
would want anyway, but we already had this discussion several times,
so I only ported
Processing commands for [EMAIL PROTECTED]:
severity 369222 grave
Bug#369222: libasound2: symbol snd_pcm_hw_params_set_channels_near not defined
in file libasound.so.2
Severity set to `grave' from `important'
merge 369040 369222
Bug#369040: libasound2: 78 symbols have gone weak, making all
Your message dated Sun, 28 May 2006 08:04:18 -0500
with message-id [EMAIL PROTECTED]
and subject line Fixed
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 responsibility to reopen the
su, 2006-05-28 kello 03:14 -0700, Steve Langasek kirjoitti:
Is there any progress on this bug?
Hi Steve,
Kenshi and I discussed this issue during Debconf.
Basically, 90% of the Ubuntu package for CUPS 1.2.0 can be used as-is
for Debian (one notable difference being that Debian does NOT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 25 May 2006 09:53:54 +0200 Marc 'HE' Brockschmidt wrote:
This bug has been open for ages now, even though Don gave a hint for
an (ugly) solution - building the package actually succeeds if
libhtml-parser-perl (which contains
fix_intltool.dpatch
Description: Binary data
If someone who can reproduce the build loop, please try the attached
patch.
TIA
-Andrew
Michel
Thanks a lot for answering.
On Sun, May 28, 2006 at 02:12:06PM +0200, Michel Dänzer wrote:
On Sat, 2006-05-27 at 01:38 +0200, Wolfgang Pfeiffer wrote:
On an updated unstable Debian, PB5,8, X only starts now with
Loaddri
disabled in xorg.conf. What's the Debian package that
Processing commands for [EMAIL PROTECTED]:
notfound 366044 3.23.49-8.15
Bug#366044: SECURITY: MySQL Anonymous Login Handshake - Information Leakage
Bug marked as not found in version 3.23.49-8.15.
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Steve and CUPS maintainers,
At Sun, 28 May 2006 03:14:31 -0700,
Steve Langasek wrote:
Is there any progress on this bug? The cupsys packages have been out of
I'm sorry for my delaying. I'm preparing to upload CUPS 1.2.1 to
experimental (then
severity 368269 normal
tags 368269 + moreinfo
thanks
Hello
On 2006-05-21 F.A.G. Luteijn wrote:
After upgrading to 0.98.3-7.2 all propagated routes are not imported
into the routingtable. I downgraded to 0.98.3-7 and I have got the
routes of my firewall back. After upgrading again I have lost
Processing commands for [EMAIL PROTECTED]:
severity 368269 normal
Bug#368269: quagga: ripd does not update routing table with propagated routes
Severity set to `normal' from `grave'
tags 368269 + moreinfo
Bug#368269: quagga: ripd does not update routing table with propagated routes
There were
retitle 368226 Quagga does intentionally not upgrade automatically
severity 368226 wishlist
tags 368226 + confirmed wontfix
thanks
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
I tried to install printconf and then to start it, but I get the
following message:
*** glibc detected *** double free or corruption (!prev): 0x081795c8
*** Unable to read printer database. Please ensure the foomatic-db
package is installed properly.
and foomatic-db is installed
Processing commands for [EMAIL PROTECTED]:
retitle 368226 Quagga does intentionally not upgrade automatically
Bug#368226: quagga - fails to upgrade
Changed Bug title.
severity 368226 wishlist
Bug#368226: Quagga does intentionally not upgrade automatically
Severity set to `wishlist' from
Your message dated Sun, 28 May 2006 09:17:12 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#338369: fixed in libcgi-formbuilder-perl 3.03.01-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
Package: bugs.debian.org
Severity: serious
this bug is fixed for 4.1; with these changes you invalidate the
information kept in the Debian BTS. Please fix it, or stop it.
If you do want to do it correct, you have to keep information, which
package is built from which branch.
[EMAIL PROTECTED]
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.20
tags 368544 experimental
Bug#368544: linux-headers-2.6.17-rc3-amd64-k8: depends on non-existant package
linux-kbuild-2.6.17
There were no tags set.
Bug#368667: unmet dependencies:
Le Dim 28 Mai 2006 18:50, Matthias Klose a écrit :
Package: bugs.debian.org
Severity: serious
this bug is fixed for 4.1; with these changes you invalidate the
information kept in the Debian BTS. Please fix it, or stop it.
If you do want to do it correct, you have to keep information, which
Processing commands for [EMAIL PROTECTED]:
tags 369088 + fixed
Bug#369088: FTBFS: build-depends xlibmesa-glu-dev no longer exists
There were no tags set.
Tags added: fixed
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
Your message dated Sun, 28 May 2006 10:17:13 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#368018: fixed in libshout 2.2-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]:
# Automatically generated email from bts, devscripts version 2.9.20
found 349354 2.6.15-8
Bug#349354: initramfs-tools - kernel -udev dependency loop
Bug marked as found in version 2.6.15-8.
End of message, stopping processing here.
Please contact me
From previous mail, in printconf code:
95 printdb = foomatic.foomatic.get_printer_db()
foomatic.foomatic.get_printer_db() is declared in foomatic.py as:
247 def get_printer_db():
248 handler = FoomaticOverviewHandler()
249 try:
250
Processing commands for [EMAIL PROTECTED]:
tags 358289 + pending
Bug#358289: FTBFS with G++ 4.1: extra qualification other problems
There were no tags set.
Tags added: pending
tags 367045 + pending
Bug#367045: rezound: FTBFS on i386/sid; build-depends on nonexistent
xlibmesa-glu-dev
Tags
Processing commands for [EMAIL PROTECTED]:
tag 367045 + fixed
Bug#367045: rezound: FTBFS on i386/sid; build-depends on nonexistent
xlibmesa-glu-dev
Tags were: pending fixed patch sid
Tags added: fixed
quit
Stopping processing here.
Please contact me if you need assistance.
Debian bug
Processing commands for [EMAIL PROTECTED]:
severity 365455 important
Bug#365455: pushing 2.6.16 into testing and the powerpc situation ...
Severity set to `important' from `grave'
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system
severity 365455 important
thanks
On Sun, Apr 30, 2006 at 09:51:29AM +0200, Sven Luther wrote:
It seems 2.6.16 is going to be pushed into testing soon, and i have some
reservations about this fact.
You had one month to fix it. As we can't longer wait, we have to ignore
this.
Bastian
--
No
Package: fai-nfsroot
Version: 2.10.1
Severity: grave
Tags: patch
Justification: renders package unusable
In dhcp3-client (3.0.4-2) the file /etc/dhcp3/dhclient-script has been
moved to /sbin. As this file has to be diverted by fai-nfsroot, the
installation now fails. Please consider applying the
On Mon, May 29, 2006 at 12:20:00AM +0900, Kenshi Muto wrote:
At Sun, 28 May 2006 03:14:31 -0700,
Steve Langasek wrote:
Is there any progress on this bug? The cupsys packages have been out of
I'm sorry for my delaying. I'm preparing to upload CUPS 1.2.1 to
experimental (then will upload to
Processing commands for [EMAIL PROTECTED]:
reassign 369257 general
Bug#369257: remote bug tracking system doesn't look at versions
Bug reassigned from package `bugs.debian.org' to `general'.
severity 369257 normal
Bug#369257: remote bug tracking system doesn't look at versions
Severity set to
Processing commands for [EMAIL PROTECTED]:
tag 362959 =
Bug#362959: bygfoot: hangs at 100% CPU, allocates all memory.
Tags were: unreproducible
Tags set to:
tag 362959 + patch
Bug#362959: bygfoot: hangs at 100% CPU, allocates all memory.
There were no tags set.
Tags added: patch
thanks
tag 362959 =
tag 362959 + patch
thanks
I confirm. I have tracked that issue down, it's because upstream takes
pointer on things that should be gsizes (aka 64 bits on amd64) on things
that are gints (32bits).
it had the nice effect to reset a loop counter to 0, hence the 100%
CPU loop.
Hi release team,
the fragroute package needs a recompile because of a libevent1
ABI change between 0.8-2 and 1.0-1.1 (without a corresponding soname
change). This is the only thing blocking grave bug #351269.
Could somebody please schedule binNMUs?
Thanks,
--
Niko Tyni [EMAIL
Hello,
I'm doing an NMU of xmon to fix #368017; diff attached.
Thanks,
Matej
diff -u xmon-1.5.6/debian/changelog xmon-1.5.6/debian/changelog
--- xmon-1.5.6/debian/changelog
+++ xmon-1.5.6/debian/changelog
@@ -1,3 +1,14 @@
+xmon (1.5.6-1.5) unstable; urgency=medium
+
+ * Non-maintainer upload.
reassign 369257 general
severity 369257 normal
thanks
On Sun, 28 May 2006, Matthias Klose wrote:
this bug is fixed for 4.1; with these changes you invalidate the
information kept in the Debian BTS. Please fix it, or stop it.
This has nothing to do with bugs.debian.org or the BTS at all. Talk
Sorry, forgot to attach the patch.
Index: debian/fai-nfsroot.dirs
===
--- debian/fai-nfsroot.dirs (revision 3484)
+++ debian/fai-nfsroot.dirs (working copy)
@@ -2,3 +2,4 @@
etc/dhcp3
etc/apt/apt.conf.d
usr/lib/fai
+sbin
Package: glibc-doc
Severity: serious
This is interesting:
# apt-get install glibc-doc
Reading package lists... Done
Building dependency tree... Done
The following NEW packages will be installed
glibc-doc
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/3354kB of
Package: php-net-smtp
Severity: serious
Justification: Policy 2.2.1
php-net-smtp recommends php-auth-sasl which is not available in Debian. This
is a serious policy violation. Section 2.2.1 states that every package in main
must not require a package outside of main for compilation or execution.
Processing commands for [EMAIL PROTECTED]:
tag 361605 patch moreinfo
Bug#361605: php4-sqlite: sqlite_escape_string tries to consume infinite memory
(and dies) on amd64
There were no tags set.
Tags added: patch, moreinfo
thanks
Stopping processing here.
Please contact me if you need
tag 361605 patch moreinfo
thanks
Matt Brown [EMAIL PROTECTED] writes:
On amd64 the sqlite_escape_string function is faulty and causes PHP to
kill the script due to PHP's internal memory limit being reached.
[...]
php5-sqlite (linked against the same libsqlite0) is not affected and
neither is
Package: amarok-xine
Version: 1.4.0a-1
Severity: grave
Justification: renders package unusable
Starting amarok, selecting a file and pressing play crashes the program.
I get the following message in the console:
amarok: relocation error: /usr/lib/xine/plugins/1.1.1/xineplug_ao_out_alsa.so:
Your message dated Sun, 28 May 2006 22:54:05 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#369275: amarok-xine: Amarok crashes when playing a file
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
Your message dated Sun, 28 May 2006 14:06:30 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#368222: fixed in xbat 1.11-11
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]:
tag 362296 patch
Bug#362296: x-ttcidfont-conf: X11R7 transition
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, Debian Bugs
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.19
reassign 369275 libasound2
Bug#369275: amarok-xine: Amarok crashes when playing a file
Bug reassigned from package `amarok-xine' to `libasound2'.
merge 369275 269222
Bug number
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.19
severity 369273 important
Bug#369273: php-net-smtp: Recommends a non-existent package.
Severity set to `important' from `serious'
End of message, stopping processing here.
Please
Your message dated Sun, 28 May 2006 14:04:40 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#358306: fixed in libgd2 2.0.33-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
Package: postgresql-common
Version: 53
Severity: grave
Justification: renders package unusable
Since the upgrade from postgresql-common 50 to 53 I cannot stop/start
my postgresql-8.0 (8.0.7-2) database anymore:
svr01:~# /etc/init.d/postgresql-8.0 start
Starting PostgreSQL 8.0 database server:
On Tue, 2006-05-23 at 12:36 +0200, Thijs Kinkhorst wrote:
Problem is that Jeroen announced that he's on a trip through Mexico
now,
so I'm left without someone to upload. Maybe the (testing) security
team
or any other DD interested in getting this bug fixed, can take a look
and upload?
Processing commands for [EMAIL PROTECTED]:
tag 368017 + fixed
Bug#368017: xmon: debmake is deprecated
Tags were: patch
Tags added: fixed
quit
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
Processing commands for [EMAIL PROTECTED]:
Version: 2.28-2
Unknown command or malformed arguments to command.
reassign 369271 manpages-dev 2.28-1
Bug#369271: glibc-doc: Filenames coincide with manpages-dev
Bug reassigned from package `glibc-doc' to `manpages-dev'.
quit
Stopping processing
Package: amarok
Version: 1.4.0a-1
Followup-For: Bug #369275
This bug happens with libasound2_1.0.11-5_i386.deb, with the older version
libasound2_1.0.11-4_i386.deb amarok works fine.
Walter
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500,
tag 362296 patch
thanks
* Steve Langasek [Sun, 21 May 2006 12:05:35 -0500]:
On Sun, May 21, 2006 at 07:37:50AM -0700, Ian Zimmerman wrote:
With the fix by David Nusinow, systems that have not transitioned are
broken. Please either look in both places for the encoding directory,
or else
Package: boinc-client
Version: 5.4.9-1
Severity: grave
Justification: renders package unusable
starting from today, when i run boinc, it starts and tries to resume
a task but immediately exits giving the followinf error (repeated
several times):
SIGSEGV: segmentation violation
Stack trace (64
On Sun, May 28, 2006 at 11:02:18PM +0200, Thijs Kinkhorst wrote:
On Tue, 2006-05-23 at 12:36 +0200, Thijs Kinkhorst wrote:
Problem is that Jeroen announced that he's on a trip through Mexico
now,
so I'm left without someone to upload. Maybe the (testing) security
team
or any other DD
tag 346233 + unreproducible
severity 346233 important
thanks
On Sun, May 21, 2006 at 02:08:35AM -0500, Enrico Zini wrote:
Hello,
I just tried to reproduce this build failure on my i386 laptop, but I
couldn't: the package built just fine.
Ciao,
I can't either in a current unstable
severity 362586 grave
# if we merge it'll get reported again and again :-(
block 366254 by 362586
thanks
To sum up, printconf calls foomatic.foomatic.get_printer_db():
/usr/bin/printconf:95: printdb = foomatic.foomatic.get_printer_db()
foomatic.foomatic.get_printer_db() invokes
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.20
retitle 366870 FTBFS: ncurses-ruby: cp: cannot stat
[..]/debian/tmp/usr/lib/ruby/1.8: No such file or directory
Bug#366870: raggle: crash at startup
Changed Bug title.
End of
Hi folks,
Is there any progress on this bug? This is currently among the issues
blocking us from having an installable desktop task for amd64 in sarge,
since there are currently no hal binaries at all in testing for this
architecture.
It would also be nice if people wouldn't take bug
Hi,
apologies, the problem can be easily fixed. It works again after
upgrading postgresql-client-common to version 53 as well. Maybe you
should adjust the package dependencies for this.
Regards,
Bernhard
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
Yeah I noticed that after reproducing the same bug with xine-ui.
Sorry about the useless bug report.
Jerome Vizcaino
On Sunday 28 May 2006 22:54, Adeodato Simó wrote:
* Jerome Vizcaino [Sun, 28 May 2006 22:15:03 +0200]:
Hi,
Here is more information about libasound2 package:
ii
Processing commands for [EMAIL PROTECTED]:
severity 362586 grave
Bug#362586: foomatic-db-engine: foomatic-combo-xml -O -l /usr/share/foomatic
aborts
Severity set to `grave' from `important'
# if we merge it'll get reported again and again :-(
block 366254 by 362586
Bug#366254: printconf:
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.20
tags 366870 + pending
Bug#366870: FTBFS: ncurses-ruby: cp: cannot stat
[..]/debian/tmp/usr/lib/ruby/1.8: No such file or directory
Tags were: moreinfo unreproducible
Tags added:
Processing commands for [EMAIL PROTECTED]:
tag 346233 + unreproducible
Bug#346233: FTBFS: guile-gnome-platform: debuild fails, guile-gnome-gw-atk.c
There were no tags set.
Tags added: unreproducible
severity 346233 important
Bug#346233: FTBFS: guile-gnome-platform: debuild fails,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: arts
Version: 1.5.3-1
Severity: Grave
Justification: No sound in KDE
Hi,
I'm Ramiro Cano.
Since the last dist-upgrade, artsd always crashes when trying to play
any sound. So, it happens that it begins to open KDE crash windows until
I
Your message dated Sun, 28 May 2006 15:02:08 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#368876: fixed in ppxp 0.2001080415-15
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
Processing commands for [EMAIL PROTECTED]:
reopen 369257
Bug#369257: remote bug tracking system doesn't look at versions
Bug reopened, originator not changed.
severity 369257 serious
Bug#369257: remote bug tracking system doesn't look at versions
Severity set to `serious' from `normal'
* Jerome Vizcaino [Mon, 29 May 2006 00:00:46 +0200]:
Sorry about the useless bug report.
No problem.
--
Adeodato Simó dato at net.com.org.es
Debian Developer adeodato at debian.org
Acaba de...
Acaba de una vez...
Acaba de
Package: f-spot
Version: 0.1.11-1
Followup-For: Bug #358551
Error on startup:
$ f-spot
Starting new FSpot server
System.DllNotFoundException: intl
in (wrapper managed-to-native) Mono.Posix.Catalog:gettext (intptr)
in 0x0002d Mono.Posix.Catalog:GetString (System.String s)
in 0x000a4
1 - 100 of 112 matches
Mail list logo
