** /home/cobb/.reportbugrc:
reportbug_version 2.63
mode advanced
ui text
realname Graham Cobb
email [EMAIL PROTECTED]
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux
Package: simh
Version: 3.6.1-1
Severity: normal
Any news on when a vax image with ethernet support will be available?
I presume the problem is the same pcap problem mentioned in the README.Debian...
Note that the pdp11-ether can't be built at this time.. The version of
libpcap that it requires
I have just upgraded Samba in etch (testing) and I get this same segfault, for
the same reason.
In my case I have never played with the passdb backend setting in smb.conf
and the upgrade did display a message saying that is was removing guest from
the setting. However, it left the line
Package: logwatch
Version: 7.1-2
Severity: important
After recently upgrading logwatch (in etch), the root partition fills up each
night
due to excessive sized temporary files genereated by logwatch. This did not
occur
before the upgrade.
The main culprit seems to be the logwatch check for
On Tuesday 26 August 2008 21:20:12 Jeff Dike wrote:
A symbol clash between libc and the kernel. Try this:
...
The patch itself didn't apply for me (probably because I copy/paste'd it from
the email) but making the change by hand to the Makefile worked and fixed the
problem.
--
To
The bisection is complete. It took longer than I expected as many of the
versions git-bisect wanted to test would not build UML without tracking down
some additional patches.
The bug seems to have been introduced with git commit
396fe6767f15141ab2dc3b933721c636c212 (uml: cover stubs with
Package: linux-image-2.6.25-2-amd64
Version: 2.6.25-7
Severity: normal
I use an AMD64 Debian lenny system to develop software for the Nokia Maemo
environment. The Maemo SDK uses scratchbox to provide cross-compilation.
Until the latest lenny update, I used scratchbox, and the Maemo SDK, in a
Package: user-mode-linux
Version: 2.6.24-1um-1
Severity: minor
I was attempting to rebuild user-mode-linux from source but choosing the
UML-specific kernel option to link the image statically.
The build failed at the link stage with the following messages:
LD init/built-in.o
LD
On Wednesday 13 August 2008 23:19:05 Mattia Dongili wrote:
can you try building 2.6.26 from unstable?
Exactly the same problem:
LD init/built-in.o
LD .tmp_vmlinux1
/usr/lib/gcc/i486-linux-gnu/4.3.1/../../../../lib/libc.a(strrchr.o): In
function `rindex':
(.text+0x0): multiple
On Thursday 14 August 2008 12:36:19 Mattia Dongili wrote:
Sorry I didn't ask for this before, but can you attach your .config?
Also, are you using make-kpkg, or are you rebuilding the binary package
from the source (i.e.: using dpkg-buildpackage)? Or are you just using
plain make?
config
Package: user-mode-linux
Version: 2.6.24-1um-1
Severity: normal
I use Debian lenny guest environment in UML to automatically build software
for the Nokia Maemo environment.
The overnight all work fine using UML 2.6.24-1um-1. However, UML
2.6.25-1um-2 and UML 2.6.26-1um-2 both crash, early in
After reading bug 491911 I tried rebuilding UML using kernel snapshot 2.6.26
3~snapshot.12089. The identical problem still occurs.
Graham
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
From reading the kernel vdso code I discovered that there is a kernel command
line option to disable vdso for 32-bit applications in the 64-bit kernel:
vdso32=0.
This fixes my problem, although I couldn't find any documentation mentioning
this option. I will suggest to the scratchbox team
Package: linux-image-2.6.22-3-amd64
Version: 2.6.22-6
Severity: important
I recently upgraded to the latest lenny kernel: 2.6.22-3-amd64. This evening,
during a period of about 40 minutes, I have had the same kernel BUG occur
5 times. The most recent two are shown in the kernel log extract
Package: libasound2
Version: 1.0.8-1
Severity: important
Since upgrading sarge recently, ALSA applications (including alsaplayer and the
KDE sound system) cannot start on my
system, which is using the Aureal Vortex (au8830) sound driver.
Applications log the following errors:
ALSA lib
Package: rss2email
Version: 1:2.54-2
Severity: normal
r2e run in cron job fails with the following log...
=== SEND THE FOLLOWING TO [EMAIL PROTECTED] ===
E: could not parse http://www.spy.org.uk/spyblog/index.xml
Traceback (most recent call last):
File /usr/share/rss2email/rss2email.py, line
Package: linux-image-2.6.21-2-686
Version: 2.6.21-6
Severity: normal
When running user mode linux (particularly more than one instance) uml reports
tasks failing with random segfaults. Apparently this is a symptom of a known
kernel bug: fault information pollution.
There is a patch for the
Package: boinc-client
Version: 5.10.8-1
Severity: important
Just upgraded my amd64 system running lenny. I noted that the boinc-client
changelog said that i686-pc-linux-gnu is now automatically used as an
alternative platform name and so the previous mechanisms for pretending
to be a
Thanks for the info. Unfortunately, the whole purpose of the previous
workround was to deal with unresponsive server administrators: if they were
not unresponsive they could easily have packaged up their i686 images into a
package for x86_64 platforms without even recompiling! The problem was
I have been running 2.6.22 (from unstable) for one week now and this problem
has not recurred. When will 2.6.22 make it into lenny?
Graham
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: linux-image-2.6.21-2-amd64
Version: 2.6.21-6
Severity: important
My AMD64 dual core system hosts a backup disk (SATA) and every night it takes
a local backup and is also accessed over NFS by another system which writes a
backup. Every few days, the system has hung or crashed when I go
On Tuesday 28 August 2007 11:18, maximilian attems wrote:
why are your reporting against that old image,
fetch 2.6.22 from unstble.
Maks,
I run testing, not unstable. If the problem is fixed in 2.6.22 that is good
to know. If you are asking me to test out the unstable kernel to report
On Thursday 11 January 2007 10:00, maximilian attems wrote:
On Sun, 21 May 2006, Graham Cobb wrote:
Package: linux-image-2.6.15-1-amd64-k8-smp
Version: 2.6.15-8
Severity: important
I am seeing occasional overnight system hangs. At least one has been
caused by the following kernel
On Monday 13 November 2006 20:31, Roberto C. Sanchez wrote:
Could it have something to do with the number of bugs against a package?
That is, if the package has a very large number of bugs on its BTS page,
could it simply be that it is taking a long time to download them all?
I don't think so.
Package: openssh-server
Version: 1:4.7p1-8
Severity: normal
I recently upgraded my lenny system with the latest openssh-server and all my
remote invocation scripts broke!
It seems that sshd no longer sources the user's .profile before executing a
command. This means that, for example, there is
It turns out that this was my problem. sshd has never executed my .profile
and the change in behaviour was because I made another change (while busy
generating new keys) and accidentally removed my .ssh/environment file.
Sorry for the bad bug report.
--
To UNSUBSCRIBE, email to [EMAIL
Package: samba
Version: 1:3.0.28a-3
Followup-For: Bug #462543
I have just upgraded to the latest samba in lenny and I cannot access any cups
printers.
If I include the lines:
load printers = yes
printing = cups
printcap name = cups
in my smb.conf then no printers are set up. The
Package: e2fsprogs
Version: 1.38+1.39-WIP-2006.04.09-1
Followup-For: Bug #366017
I also see this problem. The following command:
mke2fs -c -c -j -L backup500 /dev/sdb1
Gives the following output:
mke2fs 1.39-WIP (09-Apr-2006)
Filesystem label=backup500
OS type: Linux
Block size=4096 (log=2)
Package: knotes
Version: 4:3.5.2-1+b1
Severity: normal
When using the following command:
dcop kontact KNotesIface killNote libkcal-42915484.547 1
to try to delete a Note, the operation has no effect.
If the 'force' parameter is left off or is specified as 0, knotes correctly
prompts for
Package: linux-image-2.6.16-2-amd64-k8-smp
Version: 2.6.16-17
Severity: important
During an rm -rf of a large directory tree, kernel logged an oops. Any
subsequent access to that disk hangs.
It is likely that a similar rm -rf of the same directory tree was already
in progress at the time. Note
Package: linux-image-2.6.15-1-amd64-k8-smp
Version: 2.6.15-8
Severity: important
I am seeing occasional overnight system hangs. At least one has been caused
by the following kernel problem (syslog entry follows)...
May 21 01:30:39 black kernel: 3BUG: soft lockup detected on CPU#1!
May 21
Fixed in Opensync SVN
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Fix now in Opensync SVN
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: libatlas3gf-sse2
Severity: important
I am upgrading my squeeze system using aptitude safe-upgrade. I have no
idea what libatlas3gf-sse2 is but it has come up with the following message
during installation:
- Start of message -
The running cpu cannot execute SSE2 code
You are
The aptitde safe-upgrade eventually completed but with an error message:
dpkg: error processing libatlas3gf-sse2 (--configure):
subprocess post-installation script returned error exit status 30
I then tried removing the package with aptitude remove libatlas3gf-sse2.
This was successful and no
Package: swat
Version: 2:3.3.3-1
Severity: minor
During installation of swat, the following message is output:
- IMPORTANT INFORMATION FOR XINETD USERS --
The following line will be added to your /etc/inetd.conf file:
aptitude why libatlas3gf-sse2
i gimp Dependspython-gtk2 (= 2.8.0)
i A python-gtk2 Recommends python-numpy
i A python-numpy Dependsliblapack3gf | liblapack.so.3gf |
libatlas3gf-base
p
Package: alsa-base
Version: 1.0.23+dfsg-2
Severity: normal
My system was working fine with Squeeze, all the way through to the final
release. Sound works fine using the NVidia CK804 with ALC850 integrated in
my motherboard.
As soon as I upgraded to the wheezy testing release, however, the sound
Package: dhcp
Version: 2.0pl5dfsg1-20
Severity: normal
sysv-rc in Squeeze tries to migrate startup processing to a dependency-based
system. To do so, it analyses the currently installed init scripts.
The init script for dhcp does not meet the requirements, so the migration
fails. sysv-rc
Package: scratchbox-core
Version: 1.0.17
Severity: normal
sysv-rc in Squeeze tries to migrate startup processing to a dependency-based
system. To do so, it analyses the currently installed init scripts.
The init script for dhcpscratchbox-core does not meet the requirements, so the
migration
Package: libdevmapper1.02
Version: 2:1.02.08-1
Severity: normal
sysv-rc in Squeeze tries to migrate startup processing to a dependency-based
system. To do so, it analyses the currently installed init scripts.
The init script for libdevmapper1.02 does not meet the requirements, so the
On Thursday 26 November 2009 20:12:24 Stefan Ritter wrote:
it seems that scratchbox-core isn't in the Debian pool. Did you install
it from the upstream homepage
(http://www.scratchbox.org/download/files/sbox-releases/apophis/deb/)?
Ah, good point. I actually installed it from the repository
Package: wordpress
Version: 2.5.1-11+lenny2
Followup-For: Bug #379561
This has become a more serious problem. In the current version of
wordpress, the setup-mysql script fails if mysql-server is not installed.
The error message is:
Could not open required defaults file: /etc/mysql/debian.cnf
Package: wordpress
Version: 2.5.1-11+lenny2
Severity: wishlist
Tags: patch
The patch attached to this email allows wp-config.php to support access
using Aliases instead of Virtual Hosts. The patch does not provide creation
of the required directories or databases or the config file however if
Package: gcj-4.4-jre-headless
Version: 4.4.1-1
Severity: important
Doing 'aptitude safe-upgrade' on my squeeze system has resulted in
gcj-4.4-jre-headless being unable to be configured. The aptitude error is:
Setting up gcj-4.4-jre-headless (4.4.1-1) ...
update-alternatives: error: alternative
Package: java-gcj-compat-headless
Version: 1.0.80-5.1
Severity: important
Doing 'aptitude safe-upgrade' has left java-gcj-compat-headless
not-configurable. The
aptitude error is:
Setting up java-gcj-compat-headless (1.0.80-5.1) ...
update-alternatives: error: alternative rmiregistry can't be
Package: grub-pc
Version: 1.96+20090725-1
Severity: normal
I hit this same problem, although less serious in my case as the system is
still bootable. I agree that the installation should have copied the
kopt= settings from /boot/grub/menu.lst. It should also have informed
the installer (e.g.
Package: ghostscript-cups
Version: 8.64~dfsg-12
Severity: normal
I hit exactly the same problem when doing a safe-upgrade of squeeze. I read
Jonas' reply but, unless I misunderstand, surely the transitional packages
gs-esp and gs-gpl should depend on ghostscript-cups so that it gets installed
On Saturday 11 July 2009 20:54:09 Jonas Smedegaard wrote:
gs-esp or gs-gpl did not ever provide a working CUPS. So they should
not depend on CUPS components. Moreover, this CUPS component is
believed to not even exist back when gs-esp and gs-gpl were real
packages.
I agree that they should
Package: python-pip
Version: 0.3.1-1
Severity: normal
I just installed and tried to use python-pip. My attempts to install two
packages both failed with the following error message:
== start of error message ==
Traceback (most recent call last):
File string, line 3, in module
I am the upstream maintainer of the export code. I have no plans to change
this behaviour as I do not want to introduce CHARSET as it is explicitly
excluded from vCard 3.0.
However, I would welcome additional information on how other software handles
this, both from the export and the import
Package: coreutils
Version: 8.5-1
Severity: important
Like many systems, my filesystem contains loops due to bind mounts (in my case
it is for scratchbox, the reporter of bug 563254 has a different reason, I
have had other reasons in the past as well).
I use a backup script called
Package: mysql-common
Version: 5.1.49-1
Severity: important
File: mysql
I have just upgraded to kde4 in Squeeze. As far as I remember, I have never
used mysql on this system before but it is now used by Akonadi.
Akonadi fails its self test complaining about an error in the MySQL server log.
On Sunday 13 September 2009 10:01:55 Raphael Hertzog wrote:
What is the package that provides the java alternative with the
rmiregistry slave ?
From looking at the output of
update-alternatives --query java
it appears to be this alternative that is causing the problem:
Alternative:
On Friday 11 September 2009 14:24:49 Raphael Hertzog wrote:
On Fri, 11 Sep 2009, Matthias Klose wrote:
the only fix I can think of would be adding conflicts to every
package listing rmiregistry et al as a slave alternative. But I
don't know these packages, so it's likely that we close this
Package: password-gorilla
Version: 1.5.3.4-1
Severity: important
I have used password-gorilla for a long time and it is my main password storage.
After upgrading to the latest wheezy version of password-gorilla, the right
click menu option labelled Copy Username to Clipboard copies the
The problem appears to be with the auto-copy feature. If Use Gorilla auto-
copy is off, in the Preferences, the username is correctly copied to the
clipboard. If it is on, then the password overwrites the username on the
clipboard by the time I can do a paste.
Note that this is NOT a second
Package: dar
Version: 2.4.0-1
Severity: normal
This is the second of my bug reports about dar 2.4 breaking existing
backup scripts (in particular, Manuel Iglesias's DAR_automatic_backup.sh
script).
In order to prevent the above error being (incorrectly) reported, my dar
backup script had to be
Package: dar
Version: 2.4.0-1
Severity: important
Upgrading to dar 2.4 has broken my (longstanding) backup script in two ways.
Note: the script is Manuel Iglesias's DAR_automatic_backup.sh, which may be
in use by others. The two problems will be reported in separate bug reports
as the actions
Package: dovecot-core
Version: 1:2.1.7-2
Severity: normal
I upgraded dovecot on my wheezy system from 1:2.0.18-1 to 1:2.1.7-2. This
broke my namespace configuration and dovecot stopped working.
I have the following configuration information in a file called
/etc/dovecot/conf.d/50-grc.conf:
Package: libavcodec-extra-53
Version: 6:0.8.3-4
Severity: important
I attempted to follow the instructions on
http://wiki.debian.org/MultimediaCodecs
to install libavcodec-extra-53, however I get the following error from apt-get:
Some packages could not be installed. This may mean that you
On Wednesday 11 July 2012 10:20:37 Fabian Greffrath wrote:
Packages in Debian should always have alternative dependdencied on
both, i.e. libavcodec53| libavcodec-extra-53. Do you have packages
from other repositories installed?
The problem appears to have been that I had not succeeded in
I have added a comment/suggestion to the upstream bug report.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: dar
Version: 2.4.2-1
Severity: important
This is a followup to 637997, which is now archived so opening a new bug.
My earlier assumption that this problem was caused by the bug fixed upstream
in dar 2.4 is incorrect. I have now installed dar 2.4.2.1 (Wheezy) and this
bug is still
The following script is a simpler way to reproduce the problem.
#!/bin/sh
mkdir a
touch a/test
dar -c first -g a
touch -d yesterday a/test
dar -c second -g a -A first
dar_manager -C testdb
dar_manager -B testdb -A first
dar_manager -B testdb -A second
Note that files with mtime moving backwards
Package: src:linux
Version: 3.9.6-1
Severity: important
Dear Maintainer,
After apt-get dist-upgrade from Wheezy to Jessie, could not reboot with the
new linux 3.9 kernel. The boot appeared to stop, with the console hung,
shortly after loading the nouveau graphics driver.
The lspci info for
Upstream has reported that the workround for the problem is a new option (-
ai) which was introduced in 2.4.3 (although he also reports that 2.4.4 should
be used due to a bug in 2.4.3).
Could the version with the -ai option be brought into Testing? Without this
option, anyone who sees the
Package: wine
Version: 1.4.1-4
Followup-For: Bug #690659
I have just removed wine-unstable and moved to the multiarch version of wine.
However, printing didn't work -- the printer appears in the dialog but no
fields are filled in (paper size, etc) and the buttons do nothing.
I checked the Wine
This fix has not fixed the problem I reported.
Today I currently happened to have two messages stuck in my exim sending queue
because of this problem. These messages were not my specially crafted test
messages, just normal mail messages.
Installing openssl 1.0.1e-2 on the receiving system
Package: openssl
Version: 1.0.1e-1
Severity: important
I have just upgraded my personal mail server to the latest Wheezy.
Mail submission to postfix from some local clients has stopped working.
The entry in the mail log is:
postfix/smtpd[6543]: warning: TLS library problem:
Package: openssl
Version: 1.0.1e-1
Followup-For: Bug #702635
The postfix problem can be worked around by adding:
smtpd_tls_exclude_ciphers = AES
to the postfix configuration.
By the way, in case it is relevant, the client system showing the problem is
also Debian Wheezy, using exim and
On Saturday 09 March 2013 12:27:29 Kurt Roeckx wrote:
This is problem the same problem as various other people have
reported already. My guess is that it goes away when
you do:
export OPENSSL_ia32cap=~0x200
Yes
Can you show the content of /proc/cpuinfo?
It is 4 times this (for
On Saturday 09 March 2013 14:44:38 Kurt Roeckx wrote:
So what upstream asks is to try and reproduce it with s_client.
At least 1 person reported that this fails for him:
openssl s_client -connect mail.uni-paderborn.de:465
And then send EHLO test
No, that doesn't fail for me.
I have been
On 10/11/13 10:50, Patrick Ohly wrote:
Ubuntu essentially just copies the packaging done by Tino Keitel, who
recently said that he is willing to enable KDE support if he can get
help testing that. See
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682520
I am happy to help test in a Debian
Package: firebird2.5-server-common
Version: 2.5.2.26540.ds4-15
Severity: important
I have just been upgrading an earlier Jessie system to the current version and
get the following error messages during the upgrade:
Setting up firebird2.5-server-common (2.5.2.26540.ds4-15) ...
find: The current
Package: kdepimlibs5-dev
Version: 4:4.11.5-4+b1
Followup-For: Bug #747063
I have the same problem.
This prevents upgrading (apt-get dist-upgrade fails). I believe the severity
should be set much higher.
Note that dpkg -r --force-depends kdepim-runtime allows the upgrade to work
(or, at
Package: bash
Followup-For: Bug #763164
I have upgraded to bash 4.3-11 and this problem is no longer reproducible.
I notice in the changlog that the initial Shellshock fixes have been
replaced with upstream patches, which presumably work a bit differently.
I believe this bug can be closed.
--
Package: bash
Version: 4.3-9.2
Severity: important
I just upgraded to the bash with fixes for Shellshock. All my bash invocations
now produce multiple error messages of the form:
error importing function definition for `BASH_FUNC_a-b'
These errors are reported for all exported functions who's
Additional info:
The error messages cause MANY other scripts and programs to fail. For
example, 'update-initramfs' now fails (which causes 'apt-get install' to
also fail).
The only fix is to delete all the functions with hyphens and other
punctuation in their name using 'unset -f '.
--
To
Package: emacs21
Version: 21.4a+1-5.7
Followup-For: Bug #528363
This is happening to me every few minutes now. It seems to be the same
problem. Here is the stacktrace...
(gdb) bt
#0 __lll_lock_wait_private () at
../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95
#1 0x7fd97c0c6486
Package: github-backup
Version: 1.20141110
Followup-For: Bug #772043
I just upgraded from jessie to stretch and github-backup is now useless:
github-backup GrahamCobb
Usage: github-backup [USERNAME|ORGANIZATION] [--exclude USERNAME/REPOSITORY]
Backs up all forks, issues, etc of a GitHub
Package: awscli
Version: 1.4.2-1
Severity: important
Dear Maintainer,
I just upgraded from jessie to stretch. awscli now does not work...
$ aws
Traceback (most recent call last):
File /usr/bin/aws, line 15, in module
import awscli.clidriver
File /usr/share/awscli/awscli/clidriver.py,
Package: awscli
Followup-For: Bug #784798
Installed 1.7.0-1 from unstable and the error went away.
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (900, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.13-1-amd64 (SMP
Package: dovecot-sieve
Version: 1:2.2.18-1
Followup-For: Bug #792669
Please consider increasing the severity of this bug and releasing the package
with the upgraded
pigeonhole asap (probably without additional changes).
I upgraded my main personal mail server last week (after a few weeks of no
Package: boinc-app-seti
Version: 7.28~svn3106-1+b1
Severity: normal
Dear Maintainer,
I am getting the following message from BOINC Manager:
Message from server: Your app_info.xml file doesn't have a usable version of
SETI@home v8.
I assume this requires a new release of boinc-app-seti. I
Package: src:linux
Version: 4.3.5-1
Severity: normal
kernel BUG in btrfs. After BUG system hung and had to be rebooted.
Feb 24 01:53:43 black vmunix: [524578.024484] [ cut here
]
Feb 24 01:53:43 black vmunix: [524578.026952] kernel BUG at
Package: vagrant
Version: 1.8.1+dfsg-1
Severity: normal
Using the stretch version of vagrant, attempting to install the
"vagrant-libvirt"
plugin fails:
vagrant plugin install vagrant-libvirt
Installing the 'vagrant-libvirt' plugin. This can take a few minutes...
Package: github-backup
Version: 1.20160207-1
Severity: normal
To reproduce:
github-backup GrahamCobb
Gives the errors:
github-backup: Failed to query github for repos:
JsonError "failed to parse field homepage: expected String, encountered Null on
the JSON: Array [Object (fromList
Package: duplicity
Version: 0.7.07.1-1
Severity: normal
I created a Backblaze B2 Cloud Storage account and tried to use it with
duplicity. However all duplicity commands using B2 fail for me with the same
error messages:
/usr/lib/python2.7/dist-packages/duplicity/backends/b2backend.py:211:
Package: duplicity
Followup-For: Bug #830896
It turns out that the bucket name I was using on the command line included
Unicode characters: the "-" were actually some Unicode character that looked
like "-" but was not. This was because I had copied the bucket name off the
backblaze web page
Package: logwatch
Version: 7.4.1-2
Severity: normal
Tags: patch
Dear Maintainer,
I run a small mail server for which I need to have dovecot imap debug enabled.
Unfortunately, the debugging information fills up my logwatch reports.
As this is for debugging imap problems (which are quite
Package: logwatch
Version: 7.4.3-1
Severity: normal
Tags: patch
Dear Maintainer,
I am running dovecot imap on several systems. I do not think I have turned on
any special logging or debgging options. But my logwatch output is very full of
lines such as:
**Unmatched Entries**
dovecot:
Package: upnp-inspector
Version: 0.2.2+dfsg-3
Severity: normal
If I run upnp-inspector I get the following error:
Traceback (most recent call last):
File "/usr/bin/upnp-inspector", line 23, in
from coherence import __version__ as coherence_version
File
Package: softflowd
Version: 0.9.9-2
Severity: minor
The softflowd package information includes:
Homepage: http://code.google.com/p/softflowd/
That page no longer exists.
There appears to be a relevant page on Github:
https://github.com/davidediger/softflowd
-- System Information:
Debian
Apologies, Gregor, for my misunderstanding. I had thought that
libgetopt-long-descriptive-perl provided both. I have now removed
libgetopt-long-descriptive-perl from my system and the problem remains
so, of course, you are right.
By the way, I have confirmed that the problem does NOT occur on my
Package: libgetopt-long-descriptive-perl
Version: 0.100-1
Severity: important
Dear Maintainer,
I have just realised that a long-established cron job is not doing what it
should as
Getopt::Long processing of option values is broken. I do not know when this
happened.
It used to work but it no
On 10/06/17 22:21, Dominic Hargreaves wrote:
> Unfortunately we won't be able to fix either of these issues before
> stretch releases because we're past the last upload date, even if
> fixes were available.
>
> Given the last few releases of Getopt::Long have contained various
> regressions and
Package: logwatch
Version: 7.4.3+git20161207-2
Severity: minor
Tags: patch upstream
As we are all encouraged to lock down our SSH/SSL protocols further, I now
get hundreds of log lines telling me that things like key exchange methods
cannot be negotiated.
The patch below summarises the "Unable
Package: dovecot-sieve
Version: 1:2.2.35-2
Severity: normal
sieve processing crashes reproducibly with certain emails. This causes
these emails to be bounced with delivery failures.
mail.log contains the following information (backtrace manually reformatted for
readability):
Apr 26 10:04:26
Package: fetchmail
Version: 6.3.26-3
Followup-For: Bug #768843
I note that this bug appears to have caused fetchmail to be removed
from debian testing.
I have used fetchmail for many years, and continue to rely on it.
In fact it is working fine for me on my testing system, with the version
of
1 - 100 of 155 matches
Mail list logo
