Hi,
I've just encountered the same problem, as I tried to update my testing
installation:
> root@monica:~# apt-get update
> Hit http://ftp.at.debian.org testing InRelease
> Hit http://security.debian.org testing/updates InRelease
> Hit http://security.debian.org testing/updates/main Sources
> Hit
I know of at least one problem in 2.03 that's solved in 2.04, and that's
both of the programs using the RPC interface to query the status of
transmission and/or add torrents (the TransDroid app for Android and the
AutoTrans add-on for Firefox) not working with 2.03 since their RPC
requests erroneou
James Vega wrote:
> I don't see how your bug report could have happened given the above.
> vim-tiny's Conflicts (as well as the Depends on a specific version of
> vim-common) should have caused the old vim-common to be removed before
> vim-tiny was installed. Even without that, the Replaces would
Package: vim-common
Version: 1:7.1.293-3
Severity: serious
Justification: Policy 10.7.4
Vim-tiny is currently not installable since it conflicts with vim-common:
| aptsh> install vim-tiny
| Reading package lists... Done
| Building dependency tree
| Reading state information... Done
| The followin
Josip Rodin wrote:
> Hm, okay, let's clone the bug report to g++...
Looks like maildrop isn't the only program that has problems with GCC's
optimizations on ARM... :/
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=467341
--
Kurt Bernhard Pruenner --- Haendelstrasse 17 --- 4020 Linz --- Austri
Just wanted to add that of course the x86 binary package of maildrop
2.0.4-3 in testing and unstable didn't exhibit this bug when I tried it,
which is why I think that this is caused by a compiler (optimizer?) bug.
--
Kurt Bernhard Pruenner --- Haendelstrasse 17 --- 4020 Linz --- Austria
...I
Package: maildrop
Version: 2.0.4-3
Severity: important
I've found lately that whenever I upgraded to a 2.0.4 version of maildrop from
the
2.0.3 one that I was using maildrop would hang forever and chew up what little
CPU
there is on my NSLU2 instead of filing mails.
Today, I've finally broken o
Package: maildrop
Version: 2.0.3-1
Severity: serious
Justification: Policy 10.1
Upgrading maildrop from version 2.0.3 to the new version 2.0.4 in unstable
fails due to the new package trying to overwrite
/usr/bin/makedat which is already supplied by courier-base:
| Preparing to replace maildrop
Package: cwidget
Version: 0.5.5-4
Severity: important
Justification: fails to build from source
As can be seen at
http://buildd.debian.org/fetch.cgi?pkg=cwidget;ver=0.5.5-4;arch=arm;stamp=1196056073
compilation of ssprintf.cc fails horribly during "Making all in util"
with the following error:
I'm afraid I'm still getting this every few days on my ARM-powered
Linksys NSLU2... :(
Could we at least get an option to kill run-parts if after a specified
amount of time it's still not finished?
Or could it just periodically check if it's child is defunct every
minute or so as a workaround, if
10 matches
Mail list logo
