Bug#773672: manpages-dev: broken symlink breaks f.ex. erlang

2014-12-21 Thread Martin Millnert
ked to /bin/dash Versions of packages manpages-dev depends on: ii manpages 3.74-1 manpages-dev recommends no packages. Versions of packages manpages-dev suggests: ii man-db [man-browser] 2.7.0.2-3 -- no debconf information Best regards, Martin Millnert -- To UNSUBSCRIBE, email to debian-b

Bug#734322: nfs-common: utils/mount/nfsumount.c incorrectly rpc pinging remote rpc.mountd on NFSv4 umounts

2014-01-05 Thread Martin Millnert
Package: nfs-common Version: 1:1.2.6-4 Severity: normal Dear Maintainer, I ran into a NFS umount bug, verified and patched in Redhat as per [0]. In my example setup, I have a Wheezy NFS server, using NFSv4 exports, to a Wheezy client. When I umount a mount, I receive precisely the same error li

Bug#612124: Acknowledgement (libxerces2-java: Depends-line broken due to "hidden" special character)

2011-06-30 Thread Martin Millnert
On Wed, 2011-03-16 at 12:03 +0100, Niels Thykier wrote: > Hi > > Your problem is most likely that recommends are being installed by > default and libxerces2-java recommends libxerces2-java-gcj. (It could > also come from a dependency of libxerces2-java(-gcj)) > Installing recommends by default

Bug#612124: Acknowledgement (libxerces2-java: Depends-line broken due to "hidden" special character)

2011-06-30 Thread Martin Millnert
On Wed, 2011-03-16 at 11:53 +0100, Gerfried Fuchs wrote: > Hi! > > * Martin Millnert [2011-02-06 06:24:04 CET]: > > Update2: dpkg can install the .deb. > > apt-get and aptitude also can install the package. > > > Conclusion-suggestion: Dependency resolu

Bug#612124: Acknowledgement (libxerces2-java: Depends-line broken due to "hidden" special character)

2011-02-05 Thread Martin Millnert
Update2: dpkg can install the .deb. Conclusion-suggestion: Dependency resolution in apt/aptitude is broken | libxerces2-java is broken. Cheers, Martin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.deb

Bug#612124: Acknowledgement (libxerces2-java: Depends-line broken due to "hidden" special character)

2011-02-05 Thread Martin Millnert
An update. My first assumption seems to be wrong, but something else seems to be seriously wrong: root@sslvpn-test:/usr/src# aptitude why libxerces2-java gcj-4.4-base p libxerces2-java Depends default-jre-headless | java1-runtime-headless | java2-runtime-headless p gcj-4.4-jre-headless

Bug#612124: libxerces2-java: Depends-line broken due to "hidden" special character

2011-02-05 Thread Martin Millnert
Package: libxerces2-java Version: 2.9.1-4.1 Justification: renders package unusable Severity: grave root@sslvpn-test:/usr/src/adito-0.9.1# aptitude show libxerces2-java [...] Depends: default-jre-headless | java1-runtime-headless | java2-runtime-headless, libjaxp1.3-java [...] root@sslvpn-test:/

Bug#573782: Same issue, and a solution

2010-03-17 Thread Martin Millnert
and in to the Gnome session again. Regards, -- Martin Millnert signature.asc Description: This is a digitally signed message part

Bug#569236: Typo in printing of Teredo server address

2010-02-10 Thread Martin Millnert
are mixed up in the output of ipv6calc. Attached is a patch that fixes this. antici...@hsa:/usr/local/src/ipv6calc$ ipv6calc-0.73.0-modified/ipv6calc/ipv6calc -i 2001:0:5ef5:73bc:3838:17a2:a0af:fea4 2>&1 | grep 'is Teredo' Address type is Teredo and included IPv4 server address is

Bug#545231: Problem resolved by BIOS update

2009-09-26 Thread Martin Millnert
ice another type of difference though. The 2.6.26-2-amd64 kernel gave me somewhere along 760 KB of available memory, according to top. 2.6.30-1-amd64 now report the full 8 GB (4x2GB) I have. I do not know if it's related. Perhaps there was some memory mapping error of some sort, when attempti

Bug#545231: reportbug on linux-image-2.6.30-1-amd64

2009-09-05 Thread Martin Millnert
Package: linux-image-2.6.30-1-amd64 Version: 2.6.30-6 Severity: normal I have also made a video recording of the console log while the kernel boots. Don't know if that can be useful to you. It does provide more information than the below kernel log, though the format of said information isn't op

Bug#545232: Acknowledgement (linux-image-2.6.30-1-amd64: 18 minutes wait until X is ready to launch, instead of normal ~45 sec)

2009-09-05 Thread Martin Millnert
Hi, sincere apologies for this duplicated report of #545231. Unfortunate user error. Please handle as appropriate. Regards, -- Martin Millnert signature.asc Description: This is a digitally signed message part

Bug#545232: linux-image-2.6.30-1-amd64: 18 minutes wait until X is ready to launch, instead of normal ~45 sec

2009-09-05 Thread Martin Millnert
Package: linux-image-2.6.30-1-amd64 Version: 2.6.30-6 Severity: important When booting linux-image-2.6.30-1-amd64 my system takes some 18 minutes to boot through up until X is ready to launch. Normal for my system, for example on my current kernel linux-image-2.6.26-2-amd64, is some ~45 sec. I

Bug#545231: linux-image-2.6.30-1-amd64: 18 minutes wait until X is ready to launch, instead of normal ~45 sec

2009-09-05 Thread Martin Millnert
Package: linux-image-2.6.30-1-amd64 Version: 2.6.30-6 Severity: important When booting linux-image-2.6.30-1-amd64 my system takes some 18 minutes to boot through up until X is ready to launch. Normal for my system, for example on my current kernel linux-image-2.6.26-2-amd64, is some ~45 sec. I