Bug#1063688: mypy fails with a combination of argparse and glob

2024-02-10 Thread Mike Castle
Package: mypy Version: 1.0.1-1 Severity: normal X-Debbugs-Cc: dalg...@gmail.com Dear Maintainer, $ cat u.py import argparse import glob parser = argparse.ArgumentParser() parser.add_argument('-g', type=glob.glob) $ mypy u.py u.py:5: error: Argument "type" to "add_argument" of

Bug#1059546: pylint generates false positive 'import-error' with local editable modules.

2024-01-17 Thread Mike Castle
Easily replicable setup environment attached. A.tar.gz Description: application/gzip B.tar.gz Description: application/gzip

Bug#1059546: pylint generates false positive 'import-error' with local editable modules.

2024-01-17 Thread Mike Castle
Sorry. I now realize that changing my local PROMPT to be the default '$ ', I dropped an important bit of information. The file, `t.py` is NOT in the same directory as `pyproject.toml`. That is, while t.py was $HOME for the test, the pyproject.toml file and associated source was in some $RANDOM

Bug#1059546: pylint generates false positive 'import-error' with local editable modules.

2023-12-27 Thread Mike Castle
Package: pylint Version: 2.16.2-2 Severity: important Tags: upstream X-Debbugs-Cc: dalg...@gmail.com Dear Maintainer, This *might* be https://github.com/pylint-dev/pylint/issues/8829 . However, I am new to this bits of the Python eco-system, so not confident in my assessment. When trying to

Bug#1032522:

2023-12-12 Thread Mike Castle
I missed this report while researching, so I ended up filing this one: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058574 It looks like it was an upstream issue where certain code in python.el was brought into emacs 28.2, but didn't make it to 29.

Bug#1058574: Acknowledgement (emacs-el: emacs reliably hangs when editing python source with certain docstrings)

2023-12-12 Thread Mike Castle
Of course, as soon as I file the bug, THEN I find a likely duplicate: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032522

Bug#1058574: emacs-el: emacs reliably hangs when editing python source with certain docstrings

2023-12-12 Thread Mike Castle
Package: emacs-el Version: 1:28.2+1-15 Severity: important Tags: upstream X-Debbugs-Cc: dalg...@gmail.com Dear Maintainer, When editing the following file, emacs will reliably hang: $ cat bug.py def foo(self): """Foo.""" """ pass def baz(self): """Ba'r.""" pass The problem

Bug#707824: less: crashes with multiple group regex

2013-05-11 Thread Mike Castle
Package: less Version: 456-1 Severity: important Dear Maintainer, env -i TERM=$TERM less /usr/share/dict/words Then do this search: (a|b)(c|d) less crashes: *** glibc detected *** less: double free or corruption (fasttop): 0x0887edc8 *** === Backtrace: =

Bug#566539: linux-image-2.6.32-trunk-486: Minor formatting issue on info screen during update

2010-01-25 Thread Mike Castle
I do not have whiptail installed (saw no sense in having both dialog and whiptail installed). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#566539: linux-image-2.6.32-trunk-486: Minor formatting issue on info screen during update

2010-01-24 Thread Mike Castle
ii debconf 1.5.28 Debian configuration management system ii debconf-i18n 1.5.28 full internationalization support for debcon Configured to use dialog ii dialog

Bug#566539: linux-image-2.6.32-trunk-486: Minor formatting issue on info screen during update

2010-01-23 Thread Mike Castle
Package: linux-2.6 Version: 2.6.32-5 Severity: minor During the upgrade process, apt-get causes a message to display that starts with this text: │ Required firmware files may be missing│ │

Bug#563453:

2010-01-13 Thread Mike Castle
I too was hit by this change in bash 4.1, however, it is not a bug in bash but rather a bug in the script. Compare bash against ksh or zsh, for instance, and you'll see that 4.1 is now in step with those shells. I have not located the relevant specs, but given that this was an explicit and

Bug#564160: python-beautifulsoup: Consider permanently downgrading to 3.0.8

2010-01-07 Thread Mike Castle
Package: python-beautifulsoup Version: 3.1.0.1-2 Severity: normal Per the author's discussion at http://www.crummy.com/software/BeautifulSoup/3.1-problems.html, it might be seriously worth considering not even distributing the 3.1.0 series at this point in time. It seems pretty significantly

Bug#541296: migrationtools: migrate_services.pl generates invalid entry for tcp/udp echo

2009-08-13 Thread Mike Castle
On Wed, Aug 12, 2009 at 10:18:30PM -0700, Mike Castle wrote: Severity: grave Justification: causes non-serious data loss Incorrect: No data was actually *lost*, right? I think it's correct. After all the definition is: 'causes non-serious data loss', causes the loss of data on the system

Bug#541292: slapd: Upgrade to 2.4.17-1 fails if migrationtools have been used.

2009-08-12 Thread Mike Castle
Package: slapd Version: 2.4.17-1 Severity: important This bug is about 2.4.17-1, which I no longer have installed. I had to downgrade back to 2.4.11-1 for the time being. When I originally migrated to LDAP some time ago, I made use of migrationtools to move /etc files into LDAP.

Bug#541296: migrationtools: migrate_services.pl generates invalid entry for tcp/udp echo

2009-08-12 Thread Mike Castle
Package: migrationtools Version: 47-6 Severity: grave Justification: causes non-serious data loss The fix for bug#307618 actually introduced another issue. Any system that used migrationtools to load services will be unable to upgrade to slapd 2.4.17-1 (actually, anything newer than 2.4.15).

Bug#541292: migrationtools

2009-08-12 Thread Mike Castle
So, it turns out that the problem is from a Debian specific fix to migrationtools. Reference bug#307618 . It turns out that there is already another service entry for `cn=echo', that's why this one is mangled into `cn=echo+ipServiceProtocol=tcp+ipServiceProtocol=udp'. I've filed a new bug

Bug#509650: alsa-utils: typo in alsaconf startup screen

2008-12-23 Thread Mike Castle
Package: alsa-utils Version: 1.0.16-2 Severity: minor s/suopported/supported/ -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8,

Bug#507225: libldap-2.4-2: /etc/ldap/ldap.conf went missing during install

2008-11-28 Thread Mike Castle
Package: libldap-2.4-2 Version: 2.4.11-1 Severity: grave Justification: renders package unusable After installation, it was noticed that /etc/ldap/ldap.conf was missing. dpkg -L libldap-2.4-2 did not display the file, however, dpkg -c on the original .deb does show it present. dpkg -i fixed

Bug#412989: please add users and groups referenced by default udev configuration

2008-09-28 Thread Mike Castle
I'm new to Debian, and newer still to setting up LDAP at home. I was disheartened, when researching this problem, to find out that this is still a bug after 1.5 years. Right now there are five user/group references in udev that don't exist as part of the main system. They are, and come from:

Bug#473010: Also happens with x-window-manage

2008-05-13 Thread Mike Castle
When looking for temporary ways around this bug, I tried x-window-manage and got the same error: fvwm2[29972]: segfault at 0004 eip 0808517e esp bf8a1800 error 4 x-window-manage[30152]: segfault at 0004 eip 0808517e esp bfaba1f0 error 4 So I suspect a shared library issue. I've ended