Attila Kinali wrote:
Unfortunately I think it's now too late to fix this before the
release.
Yeah. I felt bad about opening a critical bug this short before the
release. But breaking devices is something that shouldnt happen.
Attila, I hope not have bricked any of your msp430 kits. I
On 2013-05-02 7:57, Luca BRUNO wrote:
Just for a bit of context for the RT, this just affects a minority of
the msp430 chips (the FR series, recently launched and based on
FRAM).
I expect most of the user to come for the Launchpad or other zigbee
related boards, which doesn't carry those FR
Processing control commands:
found -1 4.0-4
Bug #705992 {Done: Georges Khaznadar georg...@debian.org} [wims-moodle]
wims-moodle: fails to install: find: `/var/lib/moodle/lang': No such file or
directory
Marked as found in versions wims-moodle/4.0-4 and reopened.
--
705992:
Followup-For: Bug #705992
Control: found -1 4.0-4
And now we are failing on remove with the same error ...
Removing wims-moodle ...
find: `/var/lib/moodle/lang': No such file or directory
dpkg: error processing wims-moodle (--remove):
subprocess installed pre-removal script returned
Adam D. Barratt wrote:
If the change were made today and it was purely the text change, we
might just squeeze it in. NEWS.Debian will only be displayed to
people upgrading from earlier versions, so of those two options the
description would probably be more useful.
Ok, I'm currently
On 2013-05-02 9:39, Luca BRUNO wrote:
* gcc-msp430 is at the same version on sid and testing, can I target
this -4 to
unstable and let it migrate from there? Or should I build a
-3+wheezy1 in a
wheezy chroot and target t-p-u?
As the versions are the same, the update _must_ go via
Am Mittwoch, den 01.05.2013, 01:29 -0700 schrieb Vincent Cheng:
my bad. I accidently installed ttf-dejavu version 2.33+svn2514-2 from
experimental at some point. Going back to version 2.33-3 from testing placed
all bits correctly.
The package in experimental is a transitional package and
Processing commands for cont...@bugs.debian.org:
# distribution tags are not needed when version tracking does the right thing
tags 706451 - sid
Bug #706451 [python-jpylyzer] python-jpylyzer: python modules not installed
Removed tag(s) sid.
thanks
Stopping processing here.
Please contact me
Processing commands for cont...@bugs.debian.org:
found 706462 2.6.0-11
Bug #706462 [fp-compiler-2.6.0] fp-compiler-2.6.0: fails to install:
post-installation script returned error exit status 10
Bug #706459 [fp-compiler-2.6.0] fp-compiler-2.6.0: Aborts on configuration due
to missing debconf
Your message dated Thu, 02 May 2013 10:32:33 +
with message-id e1uxqot-0007tq...@franck.debian.org
and subject line Bug#706451: fixed in jpylyzer 1.9.2-1
has caused the Debian Bug report #706451,
regarding python-jpylyzer: python modules not installed
to be marked as done.
This means that you
When new mail arrives thunderbird/icedove gives a notification and
that is causing the hang. Yesterday I did not notice the hang as I did
not have thunderbird running. Today I saw a new mail notification on
the locked screen but I was not able to unlock it as it had hanged.
--
പ്രവീണ്
Processing commands for cont...@bugs.debian.org:
forwarded 706101 https://issues.apache.org/jira/browse/QPID-4798
Bug #706101 {Done: Michael Gilbert mgilb...@debian.org} [qpid-python]
qpid-python: contains DFSG-violating AMQP spec files
Set Bug forwarded-to-address to
Am Donnerstag, den 02.05.2013, 11:28 +0200 schrieb Fabian Greffrath:
The package in experimental is a transitional package and should contain
the same files as the package in testing - i.e. symlinks pointing to the
new file locations, respectively. Could you confirm this isn't the case?
Ah, I
Processing commands for cont...@bugs.debian.org:
tags 706516 pending
Bug #706516 {Done: Vincent Cheng vincentc1...@gmail.com} [wesnoth-1.10-core]
[wesnoth-1.10-core] Text in Wesnoth dialogs is unreadable, as Wesnoth can't
access font
Added tag(s) pending.
thanks
Stopping processing here.
Carlos Alberto Lopez Perez clo...@igalia.com writes:
On 01/05/13 17:32, micah wrote:
Carlos Alberto Lopez Perez clo...@igalia.com writes:
On 28/04/13 02:50, micah wrote:
I will happily sign for that. However I would like to migrate the
package scm from svn to git. I have not experience
The arm build fails in a different spot with the new version. Here's
the patch that works here and was applied to fritzing master.
Jeremy
another_arm_build_fix.patch
Description: Binary data
Processing commands for cont...@bugs.debian.org:
found 702674 0.7.12b-1
Bug #702674 {Done: Georges Khaznadar georg...@debian.org} [fritzing]
fritzing: Fails to build on arm*
Marked as found in versions fritzing/0.7.12b-1; no longer marked as fixed in
versions fritzing/0.7.12b-1 and reopened.
Processing control commands:
reassign -1 partconf
Bug #332227 [parted] yaboot-installer: install fail on open power 710
Bug #350372 [parted] dbian on power 710
Bug #352914 [parted] parted: 512 vs 2048 bytes block size dilemma
Bug reassigned from package 'parted' to 'partconf'.
Bug reassigned
Processing commands for cont...@bugs.debian.org:
severity 332227 important
Bug #332227 [partconf] yaboot-installer: install fail on open power 710
Bug #350372 [partconf] dbian on power 710
Bug #352914 [partconf] parted: 512 vs 2048 bytes block size dilemma
Severity set to 'important' from
user release.debian@packages.debian.org
usertags 706101 + wheezy-can-defer
tags 706101 + wheezy-ignore
thanks
On Sat, 2013-04-27 at 17:40 -0400, Michael Gilbert wrote:
So, this situation is quite unfortunate. I guess the only solution at
this point is wheezy-ignore?
Agreed, as upstream are
Processing commands for cont...@bugs.debian.org:
user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was
a...@adam-barratt.org.uk).
usertags 706101 + wheezy-can-defer
There were no usertags set.
Usertags are now: wheezy-can-defer.
tags 706101 +
FYI, upstream [1] provides a series of patches now which are addressing
the problem and should fix it both for remote and local filesystems
which can be affected under certain circumstances as well.
The developer is asking everyone who was affected, especially people
deploying GNOME in a
Processing control commands:
found -1 0.9.7.8
Bug #706641 [apt,libgd-text-perl] apt, libgd-text-perl: fails to upgrade from
squeeze: Could not perform immediate configuration on 'libgd-gd2-perl'. [i386]
There is no source info for the package 'libgd-text-perl' at version '0.9.7.8'
with
Package: tpp
Version: 1.3.1-2
Severity: grave
Tags: security
Please feel free to downgrade the bug report or remove the
security tag. It's just my point of view.
Opening an untrusted input file may be harmful, because tpp
supports an exec command, which can do bad things, e.g.
sending your
Thank you Andreas,
I removed the obsoleted file debian/prerm: as the postinst script does
no longer create the directory /var/lib/moodle/lang (if this directory
was not created earlier by moodle's usage), it can be missing, and a
minimal environment does miss it.
Best regards,
The package has been orphaned in Debian since 2007 and abandoned by
upstream at the same time since the upstream developer and Debian
maintainer are the same person.
Popcon shows just 113 installations and there are no reverse dependencies.
I therefore suggest removing the package from
Your message dated Thu, 02 May 2013 21:17:47 +
with message-id e1uy0st-0001wo...@franck.debian.org
and subject line Bug#705992: fixed in wims-moodle 4.0-5
has caused the Debian Bug report #705992,
regarding wims-moodle: fails to install: find: `/var/lib/moodle/lang': No such
file or directory
Your message dated Thu, 02 May 2013 21:17:53 +
with message-id e1uy0sz-0001zy...@franck.debian.org
and subject line Bug#706501: fixed in zelig 4.1-3-2
has caused the Debian Bug report #706501,
regarding zelig: missing build-depends on r-cran-sandwich
to be marked as done.
This means that you
On Wed, 2013-05-01 at 23:05 +0100, Steven Chamberlain wrote:
I noticed (by chance) there is a problem with the squeeze-security
patch for #690319; it introduces a regression on kfreebsd and has not
built. I'm not sure where to find build logs of this, or if they are
public, but I think it is
Hi Andreas,
as you referenced #645713 directly you probably tried this already,
but does adding the wheezy sources to sources.list instead of
replacing the squeeze ones help?
--
Richard
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe.
Package: file-rc
Version: 0.8.15
Severity: serious
Hi,
If you reconfigure, install or uninstall any package that needs to
write to /etc/runlevel.conf, the complete boot sequence will set to the
default and you will lose all your changes.
Regards,
Manolo Díaz
-- System Information:
Debian
Is it possible to upload a properly fixed package into Wheezy as soon as
upstream provides a proper patch with minimal to no delay?
I mean, having a package that can destroy the user's hardware shouldn't
be in Debian at all, I think. I'd guess people would rather waive for a
piece software
Hi,
* John Paul Adrian Glaubitz glaub...@physik.fu-berlin.de [2013-05-02 23:15]:
The package has been orphaned in Debian since 2007 and abandoned by upstream
at
the same time since the upstream developer and Debian maintainer are the same
person.
Popcon shows just 113 installations and
If you reconfigure, install or uninstall any package that needs to
write to /etc/runlevel.conf, the complete boot sequence will set to
the default and you will lose all your changes.
From the package description, it seems that this behavior is rather by
design, isn't it?
The package will
On 05/03/2013 01:39 AM, John Paul Adrian Glaubitz wrote:
If you reconfigure, install or uninstall any package that needs to
write to /etc/runlevel.conf, the complete boot sequence will set to
the default and you will lose all your changes.
From the package description, it seems that this
El vie, 3 may 2013 a las 1:46 horas
John Paul Adrian Glaubitz escribió:
On 05/03/2013 01:39 AM, John Paul Adrian Glaubitz wrote:
If you reconfigure, install or uninstall any package that needs to
write to /etc/runlevel.conf, the complete boot sequence will set to
the default and you will
Whether the OpenLDAP code that depends on GnuTLS is in a separate
process from the application or not, it might still need to set
Libgcrypt thread support callbacks when it initializes GnuTLS.
Werner Koch makes the point that ideally the application (nss-pam-ldapd
or whatever) would
Package: python-pocketsphinx
Version: 0.8-2
Severity: grave
Justification: renders package unusable
python-pocketsphinx is missing a dependency on python-sphinxbase:
pabs@chianamo ~/tmp/speech-test $ cat test.py
from pocketsphinx import Decoder
HMM =
On Fri, 2013-05-03 at 01:13 +0200, Nico Golde wrote:
* John Paul Adrian Glaubitz glaub...@physik.fu-berlin.de [2013-05-02 23:15]:
The package has been orphaned in Debian since 2007 and abandoned by
upstream at
the same time since the upstream developer and Debian maintainer are the
Your message dated Fri, 03 May 2013 05:32:04 +
with message-id e1uy8be-00026h...@franck.debian.org
and subject line Bug#333448: fixed in ldap2dns 0.3.1-3+squeeze1
has caused the Debian Bug report #333448,
regarding ldap2dns: fails to install
to be marked as done.
This means that you claim
Your message dated Fri, 03 May 2013 05:32:04 +
with message-id e1uy8be-00026h...@franck.debian.org
and subject line Bug#333448: fixed in ldap2dns 0.3.1-3+squeeze1
has caused the Debian Bug report #333448,
regarding ldap2dns: postinst fails, weirdly
to be marked as done.
This means that you
41 matches
Mail list logo
