Please apply the patch ASAP, as the correct filename
to parse the data is arguably the most important part of the
configuration file and without the patch who knows what, if anything, is
being sent out. Without the correct file name string the whole package
fails. The priority of this bug
This bug should be severity serious or grave IMO. The
package doesn't work and there is no real roadmap to
help the user try and get it to work. I tried adding
every library and binary to the blacklist as they
come caused a forced prelink to choke, but it seems
never ending and when I t
Package: prelink
Version: 0.0.20090925-6
Severity: grave
Justification: renders package unusable
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
Trying to build the package to insert more diagnostic output
(reference h
I was able to get the main binary to
build by running dpkg-buildpackage first, then
make.
--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1346083621.2996
The biggest annoyance is the lack of any verbosity or
other way to trace exactly what routine is being executed.
The error occurs when trying to dump to an NFS4 directory.
I had this working before but after a system upgrade the
error is back and it is stopping the show.
What about ruby debugging
The domain name on the server hadn't been configured to
match the domain name in the client. This resulted in
corrupted ownership (owner and group) for the destination
files, and the 'chown_if_root' routine failed.
A trace of where pdumpfs was failing can be obtained
by specifying '--backtrace' a
I bought a Seagate FreeAgent Desktop 250GB drive
yesterday, attached it in about 2 minutes, formatted 3
partitions (backup, opt and mymedia), moved the music
files (about 15 gig) from the internal drive in the
laptop to the Seagate, then commenced to do some
downloading with bittorrent. After awhi
wrong bug (meant for 419175). My apologies...it's
very late / early.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package ruby-bdb caused index++ to choke on 'README_en.html':
run-parts: executing /etc/cron.weekly/0anacron
run-parts: executing /etc/cron.weekly/dhelp
terminate called after throwing an instance of 'std::out_of_range'
what(): basic_string::erase: __pos (which is 4294967295) > this->si
This time on a fresh dhelp install, the
cron weekly job crapped out. Output attached.
Subject: Anacron job 'cron.weekly' on debianx
Content-Type: text/plain; charset=UTF-8
Message-Id:
Date: Sun, 15 May 2016 07:42:42 -0400
run-parts: executing /etc/cron.weekly/0anacron
run-parts: exec
Package: backuppc
Version: 3.3.1-5
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Select status page
* What exactly did you do (or not do) that was effective (or
ineffective)?
Package: backuppc
Version: 3.3.1-5
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Run backup
* What exactly did you do (or not do) that was effective (or
ineffective)?
Ba
The weekly cron job ran successfully, and the
a new 'documents.index' file was created. The old index
size was 69,336,284, the new size was 23,835,082.
The larger size of the old index could be due to multiple
manual runs of index++ couple with some packages which may have
been removed sin
13 matches
Mail list logo
