Bug#338348: udhcpc: false option to resolvconf
Package: udhcpc
Severity: normal
System description:
- udhcpc 0.9.8cvs20050303-1
- resolvconf 1.33
Problem description (steps to proceed):
1. ifup eth0
= Interface is up,
in /etc/resolvconf/run/interface/ are the files eth0.inet,
eth0.dhcpc
2. ifdown eth0
= Interface is down,
in /etc/resolvconf/run/interface/ is the file eth0.dhcpc,
which should not be there
Proposed solution:
Change the parameter with which resolvconf is revoked:
in files /etc/dhcpc/default.bound, [..]/default.deconfig, [..]/default.renew:
resolvconf -[ad] ${interface}.udhcpc
to
resolvconf -[ad] ${interface}
If you think, this is a problem of the resolvconf-package, please
forward it to them.
Regards,
Fabian
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (900, 'testing'), (50, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14-fabian
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#519053: Mentioned bugfix works
I just patched the 2.5.4-2 debian package with the patch provided here http://developer.pidgin.im/viewmtn/revision/info/3224dd8677b28d02b866cce510941fbf67e0fcb7 and installed the new packages and Pidgin is able to log on to ICQ again. Also ICQ chat works. Steps I did: apt-get build-dep pidgin apt-get source pidgin wget -O oscar.h.patch \ http://developer.pidgin.im/viewmtn/revision/rawdiff/1a658bb7a0436b518d65b9b95116915a5511a7d3/with/3224dd8677b28d02b866cce510941fbf67e0fcb7/libpurple/protocols/oscar/oscar.h cd pidgin-2.5.4 patch -p0 ../oscar.h.patch fakeroot debian/rules binary cd .. sudo dpkg -i libpurple0_2.5.4-2_i386.deb libpurple-bin_2.5.4-2_all.deb \ pidgin_2.5.4-2_i386.deb pidgin-data_2.5.4-2_all.deb Then started pidgin and clicked reactivate button. Running debian testing. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#521121: cyrus21-common: purges /var/run/cyrus also when cyrus 2.2 is installed
Package: cyrus21-common Version: 2.1.18-5.1 Severity: important *** Please type your report below this line *** After upgrading to cyrus 2.2, the old cyrus21-* packages are automatically uninstalled. So far so good. If you however purge the package cyrus21-common, the /var/run/cyrus directory is deleted without confirmation. Thus the cyrus 2.2 mail deliver system breaks: [...] cyrus/deliver[16928]: connect(/var/run/cyrus/socket/lmtp) failed: No such file or directory [...] postfix/pipe[16927]: [...] status=deferred (temporary failure. Command output: couldn't connect to lmtpd: No such file or directory_ 421 4.3.0 deliver: couldn't connect to lmtpd_ ) If you restart cyrus2.2, it recreates the /var/run/cyrus directory and it works again. But it is not necessarily noticed if you purge old packages... (There was however a question whether I wanted to delete all user data and I said no. The /var/spool/cyrus directory was left and that part of it was fine.) -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (500, 'oldstable'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#521121: cyrus21-common: purges /var/run/cyrus also when cyrus 2.2 is installed
On 25.03.2009 01:41, Henrique de Moraes Holschuh wrote: Yeah, it is an annoying bug. But it is now too late to fix that. Just wanted to document it. Perhaps others are warned before, iff they look at the bugreport ;) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#891916: davmail: Fails to login with latest libhtmlcleaner-java version
I tried your patched version and it fixes the problem for me. I also tried building the package myself. It failed at first attempt with the following error: [javac] /usr/src/davmail-4.8.3.2554/src/java/davmail/exchange/ExchangeSession.java:510: error: cannot find symbol [javac] List contents = ((TagNode) script).getAllChildren(); [javac] ^ [javac] symbol: method getAllChildren() [javac] location: class TagNode To get it working, I needed to upgrade the htmlcleaner dependency in the pom.xml to 2.21. Then my own built version worked as well. So, please go ahead and incorporate this change into the next version. Thanks for your support! If you need something else, just let me know. Fabian
Bug#891916: davmail: Fails to login with latest libhtmlcleaner-java version
Package: davmail Version: 4.8.3.2554-1 Severity: important Dear Maintainer, * Upon upgrading libhtmlcleaner-java from 2.2-1 to 2.21-2, I cannot connect to an exchange server via IMAP any more. Using Thunderbird, an error "Login failed" pops up. * When downgrading libhtmlcleaner-java to 2.2-1, connection works. * This happens both on openjdk-8 and oracle-java-8 Do you have an idea why this is happening? Is this a problem with davmail or with libhtmlcleaner-java? Here is the log for the non-working version: 2018-03-02 14:16:35,550 DEBUG [main] davmail - OS Name: Linux Java version: 1.8.0_161 64 System tray supported Current Desktop: i3 2018-03-02 14:16:35,553 INFO [main] davmail - SWT not available, fallback to JDK 1.6 system tray support 2018-03-02 14:16:38,589 DEBUG [davmail.imap.ImapServer] davmail - Connection from /127.0.0.1 on port 1143 2018-03-02 14:16:38,596 INFO [davmail.imap.ImapServer] davmail.connection - CONNECT - 127.0.0.1:36516 2018-03-02 14:16:38,597 DEBUG [davmail.imap.ImapServer] davmail - Connection from /127.0.0.1 on port 1143 2018-03-02 14:16:38,597 INFO [davmail.imap.ImapServer] davmail.connection - CONNECT - 127.0.0.1:36518 2018-03-02 14:16:38,908 DEBUG [ImapConnection-36518] davmail.exchange.ExchangeSession - Test configuration status: 302 2018-03-02 14:16:38,908 DEBUG [ImapConnection-36516] davmail.exchange.ExchangeSession - Test configuration status: 302 2018-03-02 14:16:38,909 DEBUG [ImapConnection-36516] davmail - > * OK [CAPABILITY IMAP4REV1 AUTH=LOGIN IDLE MOVE] IMAP4rev1 DavMail 4.8.3-trunk server ready 2018-03-02 14:16:38,909 DEBUG [ImapConnection-36518] davmail - > * OK [CAPABILITY IMAP4REV1 AUTH=LOGIN IDLE MOVE] IMAP4rev1 DavMail 4.8.3-trunk server ready 2018-03-02 14:16:38,909 DEBUG [ImapConnection-36518] davmail - < 1 authenticate LOGIN 2018-03-02 14:16:38,909 DEBUG [ImapConnection-36516] davmail - < 1 authenticate LOGIN 2018-03-02 14:16:38,912 DEBUG [ImapConnection-36518] davmail - > + [...] 2018-03-02 14:16:38,912 DEBUG [ImapConnection-36516] davmail - > + [...] 2018-03-02 14:16:38,912 DEBUG [ImapConnection-36518] davmail - < [...] 2018-03-02 14:16:38,912 DEBUG [ImapConnection-36518] davmail - > + [...] 2018-03-02 14:16:38,912 DEBUG [ImapConnection-36516] davmail - < [...] 2018-03-02 14:16:38,912 DEBUG [ImapConnection-36516] davmail - > + [...] 2018-03-02 14:16:38,912 DEBUG [ImapConnection-36518] davmail - < [...] 2018-03-02 14:16:38,912 DEBUG [ImapConnection-36516] davmail - < [...] 2018-03-02 14:16:39,002 DEBUG [ImapConnection-36518] davmail - executeFollowRedirects(https://mail.example.com/owa/) 2018-03-02 14:16:39,016 DEBUG [ImapConnection-36518] davmail - executeFollowRedirects: https://mail.example.com/owa/auth/logon.aspx?url=https%3a%2f%2fmail.example.com%2fowa%2f=0 redirectCount:1 2018-03-02 14:16:39,034 DEBUG [ImapConnection-36518] davmail.exchange.ExchangeSession - Form based authentication detected 2018-03-02 14:16:39,095 DEBUG [ImapConnection-36518] davmail.exchange.ExchangeSession - Authentication form not found at https://mail.example.com/owa/auth/logon.aspx?url=https%3a%2f%2fmail.example.com%2fowa%2f=0, trying default url 2018-03-02 14:16:39,096 DEBUG [ImapConnection-36518] davmail - executeFollowRedirects(/owa/auth/owaauth.dll) 2018-03-02 14:16:39,109 WARN [ImapConnection-36518] org.apache.commons.httpclient.HttpMethodBase - Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended. 2018-03-02 14:16:39,111 ERROR [ImapConnection-36518] davmail.exchange.ExchangeSession - Authentication failed: invalid user or password 2018-03-02 14:16:39,111 INFO [ImapConnection-36518] davmail.connection - FAILED - 127.0.0.1:36518 [username] 2018-03-02 14:16:39,112 ERROR [ImapConnection-36518] davmail - Authentication failed: invalid user or password davmail.exception.DavMailAuthenticationException: Authentication failed: invalid user or password at davmail.exchange.ExchangeSession.throwAuthenticationFailed(ExchangeSession.java:750) at davmail.exchange.ExchangeSession.postLogonMethod(ExchangeSession.java:583) at davmail.exchange.ExchangeSession.formLogin(ExchangeSession.java:653) at davmail.exchange.ExchangeSession.(ExchangeSession.java:240) at davmail.exchange.dav.DavExchangeSession.(DavExchangeSession.java:500) at davmail.exchange.ExchangeSessionFactory.getInstance(ExchangeSessionFactory.java:147) at davmail.exchange.ExchangeSessionFactory.getInstance(ExchangeSessionFactory.java:94) at davmail.imap.ImapConnection.run(ImapConnection.java:139) 2018-03-02 14:16:39,113 DEBUG [ImapConnection-36518] davmail - > 1 NO LOGIN failed 2018-03-02 14:16:39,114 DEBUG [ImapConnection-36518] davmail - < LOGIN [...] 2018-03-02 14:16:39,851 DEBUG [ImapConnection-36516] davmail - executeFollowRedirects(https://mail.example.com/owa/) 2018-03-02 14:16:39,861 DEBUG [ImapConnection-36516]
