Bug#411687: O: tdb
Package: wnpp Severity: normal Due to retiring from Debian, I am orphaning this package. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.17.11 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#411686: O: pmk
Package: wnpp Severity: normal Due to retiring from Debian, I am orphaning this package. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.17.11 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#411684: O: pike7.6
Package: wnpp Severity: normal Due to retiring from Debian, I am orphaning this package. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.17.11 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#411678: O: pexts
Package: wnpp Severity: normal Due to retiring from Debian, I am orphaning this package. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.17.11 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#411685: O: pike7.7
Package: wnpp Severity: normal Due to retiring from Debian, I am orphaning this package. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.17.11 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#411677: O: nettle
Package: wnpp Severity: normal Due to retiring from Debian, I am orphaning this package. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.17.11 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#411676: O: geoip
Package: wnpp Severity: normal Due to retiring from Debian, I am orphaning this package. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.17.11 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#411682: O: pike-public.protocols.syslog
Package: wnpp Severity: normal Due to retiring from Debian, I am orphaning this package. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.17.11 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#411680: O: pike-public.parser.xml2
Package: wnpp Severity: normal Due to retiring from Debian, I am orphaning this package. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.17.11 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#411674: O: camas
Package: wnpp Severity: normal Due to retiring from Debian, I am orphaning this package. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.17.11 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#411675: O: caudium
Package: wnpp Severity: normal Due to retiring from Debian, I am orphaning this package. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.17.11 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#411679: O: pike-public.network.pcap
Package: wnpp Severity: normal Due to retiring from Debian, I am orphaning this package. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.17.11 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#411683: O: pike-public.tools.configfiles
Package: wnpp Severity: normal Due to retiring from Debian, I am orphaning this package. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.17.11 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397938: New Upstream Version 1.4.0
On Fri, 10 Nov 2006 16:06:05 +0100, Michael Mende [EMAIL PROTECTED] scribbled: Package: geoip Hello Marek, Hello, Version 1.4.0 is available since 07-Aug-2006. Please update. I am aware of that and I have it packaged, but I have made an inquire to Maxmind regarding an ABI change in their release - haven't received the answer yet. I will try to clear the issue up next week. best regards, marek signature.asc Description: PGP signature
Bug#390634: caudium: source code missing for lucene-1.2.jar?
On Sun, 15 Oct 2006 11:22:27 +0200, gregor herrmann [EMAIL PROTECTED] scribbled: On Mon, 02 Oct 2006 12:26:22 +0300, Timo Juhani Lindfors wrote: I just noticed that the caudium package includes /usr/lib/caudium/etc/classes/lucene-1.2.jar [..] I'm not sure but I think this violates DFSG #2 Agreed. As liblucene-java exists as a Debian package I think using this pacakge solves the problem. Find attached a patch that tries to implement the usage of liblucene-java instead of the pre-compiled jar (no extensive testing, no warranty). Thanks Gregor, but I'm waiting for the next upstream release of Caudium - at which point I will remove any trace of Java from the source tarball. Pike on Debian doesn't detect any JVM anyway, so there's no point in keeping the bloat around. Thanks anyway :) best regards, marek signature.asc Description: PGP signature
Bug#390634: caudium: source code missing for lucene-1.2.jar?
On Mon, 16 Oct 2006 09:07:30 +0200, gregor herrmann [EMAIL PROTECTED] scribbled: On Mon, 16 Oct 2006 08:56:10 +0200, Marek Habersack wrote: I just noticed that the caudium package includes /usr/lib/caudium/etc/classes/lucene-1.2.jar As liblucene-java exists as a Debian package I think using this pacakge solves the problem. Thanks Gregor, but I'm waiting for the next upstream release of Caudium - at which point I will remove any trace of Java from the source tarball. Pike on Debian doesn't detect any JVM anyway, so there's no point in keeping the bloat around. Sounds reasonable. Thanks anyway :) You're welcome! (PS: Maybe you should tag the bug 'wontfix'?) Nah, I'll close it anyway today. No need to tag it. thanks again :) marek signature.asc Description: PGP signature
Bug#393400: Source package contains non-free IETF RFC/I-D's
On 16 Oct 2006 13:59:26 +0200, [EMAIL PROTECTED] (Niels Möller) scribbled: Simon Josefsson [EMAIL PROTECTED] writes: It seems this source package contains the following files from the IETF under non-free license terms: nettle-1.14.orig/testsuite/rfc1750.txt Hmm. This is kind-of funny. I use this file as test input regression testing of the pseudorandomness generator, because I felt it was appropriate... I can easily replace the file by any free text file. Any suggestions? For instance, I could replace it by the GNU manifesto, subject to Permission is granted to anyone to make or distribute verbatim copies of this document, in any medium, provided that the copyright notice and permission notice are preserved, and that the distributor grants the recipient permission for further redistribution as permitted by this notice. Modified versions may not be made.. Is that acceptable? I haven't been following the debian debates on the topic very closely. As far as I'm aware, the GNU manifesto is included in debian's emacs packages, and it would look pretty silly to remove it. Anyway, in the context of Nettle, rfc1750 is not really source code, and it doesn't make much sense to modify or fix bugs in it. Niels, I will just remove the file from the Debian .orig tarball... For that I will need to either create a fake version of libnettle (i.e. 1.14.1) or ask you to release a new version upstream - this is the only way for me to be able to remove the file from the tarball and upload the .orig.tar.gz to the archive. Which way do you prefer? And I will save my opinion on such issues to myself or for private conversation. best regards, marek signature.asc Description: PGP signature
Bug#391678: ITP: asio -- a cross-platform C++ networking library
On Mon, 9 Oct 2006 10:39:46 +0800, Zak B. Elep [EMAIL PROTECTED] scribbled: Hi Marek! =) Hey, On 10/8/06, Marek Habersack [EMAIL PROTECTED] wrote: Package: wnpp Severity: wishlist Owner: Marek Habersack [EMAIL PROTECTED] * Package name: asio Version : 0.3.7 Nice to know asio's being packaged! =) However, it appears that the next release of the Boost C++ libraries (1.34) per this announcement.[0] I myself have already integrated asio into Debian's Yes, I know that, but until then - it could be a separate package. Besides, I think it might happen (like with Spirit) that there will be two parallel versions - the one in Boost and a stand-alone. Either way, it would be nice to have asio for Edgy, which won't probably happen if it isn't packaged separately. best, marek signature.asc Description: PGP signature
Bug#391678: ITP: asio -- a cross-platform C++ networking library
Package: wnpp Severity: wishlist Owner: Marek Habersack [EMAIL PROTECTED] * Package name: asio Version : 0.3.7 Upstream Author : Christopher M. Kohlhoff [EMAIL PROTECTED] * URL : http://asio.sf.net/ * License : The Boost License (http://www.boost.org/LICENSE_1_0.txt) Programming Lang: C++ Description : a cross-platform C++ networking library ASIO is a cross-platform C++ library for network programming that provides developers with a consistent asynchronous I/O model using a modern C++ approach. -- System Information: Debian Release: testing/unstable APT prefers edgy-updates APT policy: (500, 'edgy-updates'), (500, 'edgy-backports'), (500, 'edgy') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.18-mm3 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#358261: Log for failed build of caudium_2:1.4.7-14 (dist=stable)
On Sat, Apr 08, 2006 at 01:21:00PM +0200, Martin Michlmayr scribbled: reopen 358261 retitle 358261 FTBFS with GCC 4.1: Not using -fPIC to make shared lib. thanks It seems this is still there, but it worked on the official auto builder so I wonder if this is due to a) using GCC 4.1 (instead of 4.0) or b) using the unofficial archive. [checks...] Okay, I only see this error with GCC 4.1, not with 4.0. Note however that the command line below does have -fPIC - smartlink merely strips the -R parameters and passes the rest to gcc as they are. Perhaps gcc 4.1 requires the use of -fpic instead (although -fPIC should work then too...)? Automatic build of caudium_2:1.4.7-14 on em64t by sbuild/amd64 1.112 ... /build/tbm/caudium-1.4.7/smartlink gcc -shared -fPIC -R/usr/lib -L/usr/lib -R/usr/local/lib -L/usr/local/lib -R/usr/X11R6/lib -L/usr/X11R6/lib -o _Caudium.so caudium.o nb_send.o getdate.o datetime.o entparse.o scratchpad.o/usr/lib/gcc/x86_64-linux-gnu/4.1.0/libgcc.a -lc /usr/lib/gcc/x86_64-linux-gnu/4.1.0/libgcc.a /usr/bin/ld: caudium.o: relocation R_X86_64_PC32 against `is_safe' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: final link failed: Bad value collect2: ld returned 1 exit status best regards, marek signature.asc Description: Digital signature
Bug#360325: pike7.6-mysql: Uinstallable; dependency on libmysqlclient15
On Wed, Apr 05, 2006 at 08:52:51PM +1000, Richard Salts scribbled: On Tue, Apr 04, 2006 at 03:17:49PM +0200, Marek Habersack wrote: Can you elaborate, please? libmysqlclient15-off does not exist: Oops. libmysqlclient15off. The package name of the mysqlclient libraries have changed due to an incompatible symbol. OK, I will be uploading a new version of Pike soon. It seems all it needs is recompilation, since there is no libmysqlclient15off-dev. Expect a new version in incoming in about 45-90 minutes. thanks, marek signature.asc Description: Digital signature
Bug#360325: pike7.6-mysql: Uinstallable; dependency on libmysqlclient15
severity 360325 normal quit On Sat, Apr 01, 2006 at 07:54:02PM +1100, Richard Salts scribbled: Package: pike7.6-mysql Version: 7.6.69-1 Severity: important -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (600, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13.2 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) This package needs to be recompiled with a dependency on libmysqlclient15-off. Can you elaborate, please? libmysqlclient15-off does not exist: http://packages.debian.org/cgi-bin/search_packages.pl?keywords=libmysqlclient15-offsearchon=namessubword=1version=unstablerelease=all best regards, marek signature.asc Description: Digital signature
Bug#360749: ftp.debian.org: Request for pike7.4 removal from Debian
Package: ftp.debian.org Severity: normal As the maintainer of the pike7.4 package, I would like to request its removal from the Debian repositories for the unstable distribution. This package is obsolete and with the recent upload of steam, it no longer has any packages that depend upon it. thanks, marek -- System Information: Debian Release: testing/unstable APT prefers dapper-updates APT policy: (500, 'dapper-updates'), (500, 'dapper-security'), (500, 'dapper') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-18-k7 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#348546: Please remove pike7.2 from the unstable distribution
Package: ftp.debian.org Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Please remove the pike7.2 source package along with all its binary packages from the Debian/unstable distribution. The reason for the request is that pike7.2 is legacy code, no longer depended upon by any other Debian packages (with the exception of roxen3 whose removal request should follow soon) and there is little to no demand for that version of Pike in general. The current version of Pike is 7.6 with 7.8 to follow in the near future. The binary package names produced from the pike7.2 source are: pike7.2 pike7.2-crypto pike7.2-gdbm pike7.2-gl pike7.2-gtk pike7.2-gz pike7.2-image pike7.2-mysql pike7.2-odbc pike7.2-pexts-admintools pike7.2-pexts-bzip2 pike7.2-pexts-curses pike7.2-pexts-geoip pike7.2-pexts-mcrypt pike7.2-pexts-mhash pike7.2-pexts-newt pike7.2-pexts-pcre pike7.2-pg pike7.2-sane thank you, marek - -- System Information: Debian Release: testing/unstable APT prefers dapper-updates APT policy: (500, 'dapper-updates'), (500, 'dapper-security'), (500, 'dapper') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-12-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDzS7Oq3909GIf5uoRAixMAJ9xX8Lhthc9X51Fcf1wbLaT2/j3ewCePXse OuQZ0fgYXDFrVwVKBYatBfA= =N2gY -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#348546: Please remove pike7.2 from the unstable distribution
On 1/17/06, Jeroen van Wolffelaar [EMAIL PROTECTED] wrote: tags 348546 moreinforetitle 348546 RM: pike7.2 -- RoM; Superseded by pike7.6thanksOn Tue, Jan 17, 2006 at 06:52:15PM +0100, Marek Habersack wrote: Please remove the pike7.2 source package along with all its binary packages from the Debian/unstable distribution. The reason for the request is that pike7.2 is legacy code, no longer depended upon by any other Debian packages (with the exception of roxen3 whose removal request should follow soon) and there is little to no demand for that version of Pike in general. The current version of Pike is 7.6 with 7.8 to follow in the near future.pexts (pike7.2-pexts-*) does depend on it too still though? What to dowith that? I will repackage pexts after I can remove pike7.4 as well. This is awaiting input from the steam maintainer about the possibility of upgrading steam to work with pike7.6. After that pexts will lose some binary packages and the rest will be renamed to a new scheme. thanks,marek
Bug#342650: pike7.6: The pike package is present in sarge but missing from etch.
On Mon, Jan 02, 2006 at 02:33:57PM +0100, Edward Welbourne scribbled: I note with glee, upon my return from mid-winter holidays, that the pike package set now shows up among etch's New Packages (as reported by aptitude) - bug fixed, thank you :-) :) I hope to upload pike 7.7 to experimental soon, if you're interested happy new year :), marek signature.asc Description: Digital signature
Bug#345329: pike-public.parser.xml2 - FTBFS: gcc: /usr/lib/gcc/i486-linux-gnu/4.0.3/libgcc.a: No such file or directory
reassign 345329 pike7.6-core reassign 345330 pike7.6-core merge 345329 345330 stop On Fri, Dec 30, 2005 at 05:05:46PM +0100, Bastian Blank scribbled: Package: pike-public.parser.xml2 Version: 1.36-1 Severity: serious There was an error while trying to autobuild your package: It's a Pike bug. I'm in the process of compiling new pike that fixes it. regards, marek signature.asc Description: Digital signature
Bug#342650: pike7.6: The pike package is present in sarge but missing from etch.
Hello Edward, You're right, I misread your initial message and thus the confusion. You're right, pike7.6 is not in etch yet - please see http://qa.debian.org/developer.php?excuse=pike7.6 though. It should be in the testing archive really soon now. thanks for your input, regards marek
Bug#342650: pike7.6: The pike package is present in sarge but missing from etch.
severity 342650 normal thanks On Fri, Dec 09, 2005 at 11:35:28AM +0100, Edward Welbourne scribbled: Package: pike7.6 Version: 7.6.24-1 Severity: important Some months ago I upgraded from sarge to etch by simply editing sources.list and running aptitude -u; consequently, I kept the pike7.6 from before the switch. (I'm told a dist-upgrade would have removed it.) This week, I got a new machine, so set it up straight off in testing. The pike7.6 package is not present. I had to add a sarge entry back into sources.list to retrieve it ! So it's *etch*, not pike, that was rendered unusable (for me) by this omission ... I must say you got me surprised with that, because: - http://packages.debian.org/unstable/interpreters/pike7.6 http://ftp.debian.org/debian/pool/main/p/pike7.6/pike7.6_7.6.55-1_all.deb # apt-cache show pike7.6 Package: pike7.6 Priority: optional Section: interpreters Installed-Size: 36 Maintainer: Marek Habersack [EMAIL PROTECTED] Architecture: all Version: 7.6.55-1 Depends: pike7.6-core (= 7.6.55-1), pike7.6-image (= 7.6.55-1), pike7.6-gdbm (= 7.6.55-1) Recommends: pike7.6-doc (= 7.6.55-1) Suggests: pike7.6-mysql (= 7.6.55-1), pike7.6-pg (= 7.6.55-1), pike7.6-dev (= 7.6.55-1) Filename: pool/main/p/pike7.6/pike7.6_7.6.55-1_all.deb Size: 18248 MD5sum: 1c2d0ddfc332b493a49064c1a548d3b2 Description: Recommended meta package for Pike 7.6 - As you can see, the package is right there. Perhaps it's a problem with your mirror? Could you please try using some other mirror just to see whether the problem disappears? Meanwhile I'm changing the severity of the bug to normal. Please let me know about the results of your tests with the new mirror, regards, marek signature.asc Description: Digital signature
Bug#341996: ITP: public.parser.xml2 -- libxml2-based XML parser module for Pike
Package: wnpp Severity: wishlist Owner: Marek Habersack [EMAIL PROTECTED] * Package name: public.parser.xml2 Version : 1.36 Upstream Author : Bill Welliver [EMAIL PROTECTED] * URL : http://modules.gotpike.org/module_info.html?module_id=20 * License : (GPL, LGPL, MPL) Description : libxml2-based XML parser module for Pike The software is a Pike module that wraps the libxml2 and libxslt1 libraries to provide access to their functionality from Pike programs. -- System Information: Debian Release: testing/unstable APT prefers dapper-updates APT policy: (500, 'dapper-updates'), (500, 'dapper-security'), (500, 'dapper') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-6-k7 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341999: ITP: public.tools.configfiles -- Pike module for accessing ini-style configurations
Package: wnpp Severity: wishlist Owner: Marek Habersack [EMAIL PROTECTED] * Package name: public.tools.configfiles Version : 1.0 Upstream Author : Bill Welliver [EMAIL PROTECTED] * URL : http://modules.gotpike.org/module_info.html?module_id=25 * License : (GPL) Description : Pike module for accessing ini-style configurations A simple module for reading and writing ini-style configurations from within Pike programs. -- System Information: Debian Release: testing/unstable APT prefers dapper-updates APT policy: (500, 'dapper-updates'), (500, 'dapper-security'), (500, 'dapper') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-6-k7 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#342018: ITP: public.protocols.syslog -- Pike module implementing the Syslog protocol
Package: wnpp Severity: wishlist Owner: Marek Habersack [EMAIL PROTECTED] * Package name: public.protocols.syslog Version : 1.1 Upstream Author : Bill Welliver [EMAIL PROTECTED] * URL : http://modules.gotpike.org/module_info.html?module_id=7 * License : (GPL, LGPL, MPL) Description : Pike module implementing the Syslog protocol A Pike module containing functions for decoding and encoding Syslog messages. -- System Information: Debian Release: testing/unstable APT prefers dapper-updates APT policy: (500, 'dapper-updates'), (500, 'dapper-security'), (500, 'dapper') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-6-k7 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#342031: ITP: public.network.pcap -- Pike interface module for the pcap library
Package: wnpp Severity: wishlist Owner: Marek Habersack [EMAIL PROTECTED] * Package name: public.network.pcap Version : 1.2 Upstream Author : Bill Welliver [EMAIL PROTECTED] * URL : http://modules.gotpike.org/module_info.html?module_id=9 * License : (GPL, LGPL, MPL) Description : Pike interface module for the pcap library This module provides an interface to the pcap packet capture library. -- System Information: Debian Release: testing/unstable APT prefers dapper-updates APT policy: (500, 'dapper-updates'), (500, 'dapper-security'), (500, 'dapper') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-6-k7 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341391: pike7.4: FTBFS on GNU/kFreeBSD
On Wed, Nov 30, 2005 at 01:09:17PM +0100, Petr Salinger scribbled: Package: pike7.4 Severity: important Version: 7.4.341-2 Tags: patch Hi, Hello, the current version fails to build on GNU/kFreeBSD. Please find a small attached patch to fix that. It would also be nice if you can ask upstream to include this changes into pike7.4 branch. Thanks, I've already committed it to the upstream cvs and will be compiling and uploading the new version soon. thanks again, marek signature.asc Description: Digital signature
Bug#341423: pike7.6: FTBFS on GNU/kFreeBSD
On Wed, Nov 30, 2005 at 03:10:53PM +0100, Petr Salinger scribbled: Package: pike7.6 Severity: important Version: 7.6.51-2 Tags: patch Hi, Hello Thanks for CVS fix of pike7.4, similar patch is also needed for pike 7.6. Already added to the pike 7.6 cvs as well :) best regards, marek signature.asc Description: Digital signature
Bug#336383: acknowledged by developer (Bug#336383: fixed in caudium 2:1.4.7-6)
On Tue, Nov 01, 2005 at 09:55:23AM +0100, Mario 'BitKoenig' Holbe scribbled: On Mon, Oct 31, 2005 at 09:41:37AM +0100, Mario 'BitKoenig' Holbe wrote: reopen 336383 Here is a small patch which is probably more meaningful than my prosa :) Heh, thanks - I've already fixed the issue, just waited for pike7.6 to propagate before I upload the new caudium - that will happen within the next 30 minutes :) Also, removing the pidfile /var/run/caudium/caudium.pid before caudium is actually stopped (it will be stopped below), is probably not a good idea. Presumed you really think you need to remove the pidfile I just moved it below the debhelper section which in fact calls /etc/init.d/caudium stop (which, in turn, needs the pidfile :)). I moved it to postrm However, if you really think you need to remove the pidfile, plese consider doing this in the init-script after the start-stop-daemon call in the stop section. It's just a cleanup thing, it doesn't matter whether the file exists while caudium is installed, but it would be untidy to leave it behind when the package is purged :) regards, marek signature.asc Description: Digital signature
Bug#262579: #262579: samba: /usr/bin/tdbbackup conflicts with tdb-tools
On Sat, Sep 24, 2005 at 12:16:52AM -0700, Steve Langasek scribbled: On Sat, Sep 24, 2005 at 12:22:55PM +1000, Andrew Bartlett wrote: For the tdb-tools package? Well, the debian/copyright file says This package was debianized by Marek Habersack [EMAIL PROTECTED] on Mon, 7 May 2001 18:03:17 +0200. It was downloaded from http://samba.org/ This is the bit that doesn't quite add up. Upstream Author: Andrew Tridgell [EMAIL PROTECTED] And the upstream version number is 1.0.6... It appears that the debian package is the spun off version from sf.net, patched back to look like mainline Samba 3.0.5. Perhaps it would be Well, that's what's happened later on when it became apparent that the sf.net version was most probably unmaintained. better to have it built from the samba source package? Is there currently a good way to do that? The tdb-tools package seems to include some tools that aren't present in the samba 3.0.14a source/tdb/ directory, and the makefile only covers building tdbbackup, tdbdump, and tdbtool (tdbtest and tdbtorture appear to be present in the source, but not built). I don't mind building a tdb package out of the samba source tree, but I don't really know which tools have to be in it. It would indeed make more sense to build the package from the samba sources now. The tools that are, IMHO, required to be present in the package are the ones built by samba by default, tdbtest and tbtorture are quite optional and could be included just for completness. best regards, marek signature.asc Description: Digital signature
Bug#262579: #262579: samba: /usr/bin/tdbbackup conflicts with tdb-tools
On Thu, Sep 29, 2005 at 10:21:37PM +1000, Andrew Bartlett scribbled: [snip] I don't mind building a tdb package out of the samba source tree, but I don't really know which tools have to be in it. It would indeed make more sense to build the package from the samba sources now. The tools that are, IMHO, required to be present in the package are the ones built by samba by default, tdbtest and tbtorture are quite optional and could be included just for completness. So, the approach would be to get the libtdb building code from sf.net, it's just the standard autoconf code, so no problem there and add it to the already too many patches in Samba for debian. Then work with jra and jerry on making this upstream, if it can be done portably. I can't imagine building the other utilities will be a big pain. The tricky bit might be deciding to use the separate makefile or the main build system. I think the best idea would be to just create a Makefile.libtdb by hand and slam it in the source/tdb/ directory then call it separately to the main samba build process. That makefile would use libtool (although I don't really think it is necessary to use libtool here, since we're targetting platforms where gcc -shared works just fine) to create a shared version of the tdb library and to recompile/relink the utility programs against that library. The question is whether to make samba link the daemons against the shared library or leave them as they are (tdb is linked into the executables statically, along with other code). I would vote on leaving the daemons as they are as that would minimize the set of required changes to the build process. best regards, marek signature.asc Description: Digital signature
Bug#262579: #262579: samba: /usr/bin/tdbbackup conflicts with tdb-tools
On Thu, Sep 29, 2005 at 10:49:47PM +1000, Andrew Bartlett scribbled: [snip] and add it to the already too many patches in Samba for debian. Then work with jra and jerry on making this upstream, if it can be done portably. I can't imagine building the other utilities will be a big pain. The tricky bit might be deciding to use the separate makefile or the main build system. I think the best idea would be to just create a Makefile.libtdb by hand and slam it in the source/tdb/ directory This is exactly what already exists, I'm suggesting just patching the extra in. You missed my point :) - I suggest adding another Makefile in the source/tdb/ dir and not touching the original one - that way, the changes stay clear of the upstream samba code == less ado with maintaining that patch should the original Makefile change. After all, it's a Debian-specific thing we're talking about :) (especially that, as we say below, the core samba should not link against the shared tdb library - the more reason not to touch the upstream source/tdb/ Makefile IMO) then call it separately to the main samba build process. That makefile would use libtool (although I don't really think it is necessary to use libtool here, since we're targetting platforms where gcc -shared works just fine) to create a shared version of the tdb library and to recompile/relink the utility programs against that library. I would personally leave them static, but anyway. Also, I would keep I agree clear of libtool, due the general feeling against libtool upstream :-) /me is totally against libtool (and autotools in general :P) as well, and gcc -shared works really well where we need it to work. The question is whether to make samba link the daemons against the shared library or leave them as they are (tdb is linked into the executables statically, along with other code). I would vote on leaving the daemons as they are as that would minimize the set of required changes to the build process. I strongly oppose building Samba against a libtdb .so, simply because this is a very core building block, and I would not wish any changes to samba itself. I agree with you. So, Steve, your take on that? best regards, marek signature.asc Description: Digital signature
Bug#262579: #262579: samba: /usr/bin/tdbbackup conflicts with tdb-tools
On Thu, Sep 29, 2005 at 10:58:41PM +1000, Andrew Bartlett scribbled: On Thu, 2005-09-29 at 14:55 +0200, Marek Habersack wrote: On Thu, Sep 29, 2005 at 10:49:47PM +1000, Andrew Bartlett scribbled: [snip] and add it to the already too many patches in Samba for debian. Then work with jra and jerry on making this upstream, if it can be done portably. I can't imagine building the other utilities will be a big pain. The tricky bit might be deciding to use the separate makefile or the main build system. I think the best idea would be to just create a Makefile.libtdb by hand and slam it in the source/tdb/ directory This is exactly what already exists, I'm suggesting just patching the extra in. You missed my point :) - I suggest adding another Makefile in the source/tdb/ dir and not touching the original one - that way, the changes stay clear of the upstream samba code == less ado with maintaining that patch should the original Makefile change. After all, it's a Debian-specific thing we're talking about :) (especially that, as we say below, the core samba should not link against the shared tdb library - the more reason not to touch the upstream source/tdb/ Makefile IMO) The core Samba doesn't use the source/tdb Makefile. Samba compiles tdb for it's purposes from the main source/Makefile. Adding the extra targets for libtdb to the end of that file should not be too painful... Ah, ok then. I thought it was used by the upstream. Well, if so, then I guess you're right on that :) best regards, marek signature.asc Description: Digital signature
Bug#328362: pmk: postinst fails, missing depends?
On Thu, Sep 15, 2005 at 12:17:11AM +0300, Lars Wirzenius scribbled: Package: pmk Version: 0.9.3-1 pmk fails testing with piuparts. After modifying the postinst script to use set -x and removing the redirection of error messages to /dev/null in the call to pmksetup, I see the following error messages: PMKSETUP version 0.9.3 == Looking for default parameters... Error : cannot find a C compiler. Error : failed to locate binaries. Error : child failed (status 256) dpkg: error processing pmk (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: pmk At a guess, some depends are missing? Actually, it looks like a bug in pmk. The C compiler is specified in the -u BIN_C parameter passed to pmksetup which, as per documentation, should skip the data gathering stage. This is not happening, apparently. I will look into it as soon as possible, thanks for reporting. regards, marek signature.asc Description: Digital signature
Bug#326773: tdb-dev: Typo in tdb_open(3)
On Mon, Sep 05, 2005 at 06:41:02PM +0200, Ludovic Courtes scribbled: Package: tdb-dev Version: 1.0.6-13 Severity: normal The manual page for tdb_open(3) contains a small error. Regarding the `TDB_NOLOCK' flag, it should read: TDB_NOLOCK Don't do any locking (this is always turned on for read-write file descriptors) (Note `read-write' instead of `read-only'). This is odd, since the manpage inside both the development deb and in the .orig tarball has read-only there. Please check whether you don't have a stray copy of tdb installed from an earlier version tarball lurking somewhere in your /usr/local/. Here are the md5 digests for the manpage as shipped in the dev deb and the .orig tarball: 3b550dd51a06c305f6e5dc87cc41bb73 tdb_open.3.gz ca9315e681525d6ad706459d0f17cdee tdb_open.3 Please let me know about the results of your findings, I will keep this bug open till then best regards, marek signature.asc Description: Digital signature
Bug#326031: pike7.2_7.2.580-4 (arm/unstable): FTBFS: Attempt to call the NULL-value
On Thu, Sep 01, 2005 at 03:49:20AM -0700, Steve Langasek scribbled:
Package: pike7.2
Version: 7.2.580-4
Severity: serious
pike7.2 is failing to build on the arm autobuilder with the following
error:
[...]
make[4]: Entering directory
`/build/buildd/pike7.2-7.2.580/build/linux-2.4.27-netwinder-armv4l/post_modules/GTK'
/build/buildd/pike7.2-7.2.580/build/linux-2.4.27-netwinder-armv4l/pike
-DNOT_INSTALLED
-m/build/buildd/pike7.2-7.2.580/build/linux-2.4.27-netwinder-armv4l/master.pike
/build/buildd/pike7.2-7.2.580/src/post_modules/GTK/new_build_pgtk.pike
--source='/build/buildd/pike7.2-7.2.580/src/post_modules/GTK/source/'\
/build/buildd/pike7.2-7.2.580/src/post_modules/GTK/output/few.pike
Attempt to call the NULL-value
Unknown program:
0(/build/buildd/pike7.2-7.2.580/build/linux-2.4.27-netwinder-armv4l/post_modules/GTK//files_to_compile,r,438)
/build/buildd/pike7.2-7.2.580/lib/modules/Stdio.pmod/module.pmod:297:
Stdio.FILE(/build/buildd/pike7.2-7.2.580/build/linux-2.4.27-netwinder-armv4l/post_modules/GTK//files_to_compile,
r, 666 /* fd=-1
*/)-open(/build/buildd/pike7.2-7.2.580/build/linux-2.4.27-netwinder-armv4l/post_modules/GTK//files_to_compile,r,438)
/build/buildd/pike7.2-7.2.580/lib/modules/Stdio.pmod/module.pmod:1203:
Stdio.FILE(/build/buildd/pike7.2-7.2.580/build/linux-2.4.27-netwinder-armv4l/post_modules/GTK//files_to_compile,
r, 666 /* fd=-1
*/)-open(/build/buildd/pike7.2-7.2.580/build/linux-2.4.27-netwinder-armv4l/post_modules/GTK//files_to_compile,r)
/build/buildd/pike7.2-7.2.580/lib/modules/Stdio.pmod/module.pmod:1351:
read_file(/build/buildd/pike7.2-7.2.580/build/linux-2.4.27-netwinder-armv4l/post_modules/GTK//files_to_compile,0,0)
/build/buildd/pike7.2-7.2.580/src/post_modules/GTK/new_build_pgtk.pike:1527:
main(3,({/build/buildd/pike7.2-7.2.580/src/post_modules/GTK/new_build_pgtk.pike,--source=/build/buildd/pike7.2-7.2.580/src/post_modules/GTK/source/,,,0}))
make[4]: *** [compile1] Error 10
[...]
A full build log can be found at
http://buildd.debian.org/fetch.php?pkg=pike7.2ver=7.2.580-4arch=armstamp=1123905177file=logas=raw.
This is a serious bug because it is a regression on an architecture
where pike7.2 previously built successfully. Because pike7.2 blocks the
libgmp C++ ABI transition, it will most likely be removed from testing
pending resolution of this bug.
It is nearly impossible for me to debug that given just the buildd output...
If you know of any ARM emulator (qemu doesn't support ARM system emulation,
alas) or an ARM machine whose administrator would be willing to install all
the pike7.2 7.2.580 build dependencies, then I'll start working on it right
away.
regards,
marek
signature.asc
Description: Digital signature
Bug#326031: pike7.2_7.2.580-4 (arm/unstable): FTBFS: Attempt to call the NULL-value
On Thu, Sep 01, 2005 at 03:04:59PM -0700, Steve Langasek scribbled: Hi Marek, Hello Steve, On Thu, Sep 01, 2005 at 11:06:03PM +0200, Marek Habersack wrote: A full build log can be found at http://buildd.debian.org/fetch.php?pkg=pike7.2ver=7.2.580-4arch=armstamp=1123905177file=logas=raw. This is a serious bug because it is a regression on an architecture where pike7.2 previously built successfully. Because pike7.2 blocks the libgmp C++ ABI transition, it will most likely be removed from testing pending resolution of this bug. It is nearly impossible for me to debug that given just the buildd output... If you know of any ARM emulator (qemu doesn't support ARM system emulation, alas) or an ARM machine whose administrator would be willing to install all the pike7.2 7.2.580 build dependencies, then I'll start working on it right away. Since debussy.debian.org is still inconveniently off-line, I'm going to put you in touch with Kenshi Muto who also has an arm system and may be able to help you. Excellent, thanks a lot, marek signature.asc Description: Digital signature
Bug#309191: Can you check this please now?
Hello Kurt, Since the autobuilders haven't been able to build past few versions of Pike (due to missing dependencies) could you, please, compile caudium by hand on your amd64 machine (I assume you have access to one) and let me know whether the bug is gone so that I can close it? Looking at the 64 bit architectures that built caudium recently, it should be gone, but since your original report referred to amd64, I need a confirmation that it's gone there as well before closing it, thanks a lot, marek signature.asc Description: Digital signature
Bug#319889: libgphoto2-2: The library should be recompiled with the latest libexif
Package: libgphoto2-2 Severity: important The version currently in the archive depends upon libexif10, which is no longer in debian (the current libexif library package name is libexif12). In effect it makes libsane (and a host of other packages) uninstallable and that, in turn, prevents me from uploading a new version of Pike (which build-depends on libsane) that fixes an RC bug to the archive. Please recompile and upload the library ASAP, thanks a lot marek -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.10-xenU Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#310884: pike7.2: FTBFS: ../../precompile.sh: line 151: pike: command not found
[snip] Hi, As terry said, I couldn't find any problem with pbuilder and sbuild (buildd utility). I think this bug may beclosed, but just do downgrade at now. It's not because you can't reproduce this that you should lower the severity. Oops, I've just noticed that the bug was closed in an NMU. This is the result of replying to mail as you read : - don't do it at home ;) marek signature.asc Description: Digital signature !DSPAM:429a4aac50941225414837!!DSPAM:429a4aac50941439624106!!DSPAM:429a4aac50941981818450!
Bug#310884: pike7.2: FTBFS: ../../precompile.sh: line 151: pike: command not found
severity 310884 normal thanks On Fri, May 27, 2005 at 11:54:46AM +0900, Kenshi Muto wrote: severity 310884 important thanks Hi, As terry said, I couldn't find any problem with pbuilder and sbuild (buildd utility). I think this bug may beclosed, but just do downgrade at now. It's not because you can't reproduce this that you should lower the severity. On a system with correct RTC settings, with no bugs in the touch(1) utility this cannot happen. It can happen only when make(1) detects that the .c file to be generated from a .cmod source is older than the .cmod source. precompile.sh is called only in such situation or when running 'make export' on the CVS sources - in the latter case, the .c timestamp is newer than that of the .cmod. Therefore, please check your RTC and the touch(1) utility (there was a problem with it not working properly on hppa and mips long time ago, perhaps you stumbled across the same/similar problem). I haven't been able to reproduce the problem as well so I'm downgrading the bug severity to normal. Please do not raise it until you can show us a reproducible scenario to reproduce the bug, thanks marek signature.asc Description: Digital signature !DSPAM:429a4a1848381762994518!!DSPAM:429a4a1848381479334183!!DSPAM:429a4a1848381733669542!
Bug#298963: caudium: contains non-free fonts
On Thu, Mar 24, 2005 at 11:58:10AM -0300, Gustavo Franco scribbled: Hi Marek, Hello Gustavo, [damned, forgot to upload a new version...] The free fonts site that you said is corefonts.sf.net.These fonts aren't free as in DFSG and there's a package at contrib section called 'msttcorefonts', AFAIK the postinst retrieves the fonts from the website. I know, but the font I meant is not one of the MS fonts. Tere is a third font there, which was taken from a free site, whose name I cannot remember. Can't you confirm if caudium works without these and that other font ? If not we can still try the freefont alternatives or just replace the references to these fonts and test. Yes, caudium itself will work without any of the TTF fonts present. Its config interface (web-based) uses a built-in bitmapped font for rendering of some controls, the Lucida font is used by default by some modules that render text, but changing it is not a problem. I will try to remember and upload a new version that uses bitstream vera this weekend. Have you contacted upstream ? If not, please do so and point them to: http://corefonts.sourceforge.net/eula.htm I am one of the upstream authors :) - it wasn't me who put the fonts there, but I know the situation. I haven't fixed it so far merely because of lack of time in the past weeks, but I'll get to it asap. Promise. best regards, marek signature.asc Description: Digital signature
Bug#298963: caudium: contains non-free fonts
On Fri, Mar 18, 2005 at 09:55:56AM +0200, Lars Wirzenius scribbled: Peter De Wachter: This package contains three non-free fonts: I note that building the package after removing the fonts does succeed. However, since I don't know caudium at all, I haven't tested the package. Just providing a bit of information. Someone who uses caudium should download the source, remove server/fonts/ttf/*.ttf, build and install the package, and see if it still works. If it does, then an upload is in order (I'm willing to sponsor or do it myself), but if not, someone needs to figure out a way to get caudium to use some of the free ttf fonts instead. I'm sorry not to respond earlier, but I've been busy with other things and had to put the debian stuff aside for a while. Anyhow, as for the fonts, they come with a license that they are free for use, albeit (of course) not in the FSF or Debian sense, so I guess it should be removed and replaced with something else. The third font was taken by a member of the Caudium project from a free font site (I can't remember which and the member is gone with the wind, and I can't contact him) but I remember we did check whether it was free in the FSF sense. So that one can stay. The fonts are not essential to Caudium workings although their lack does limit the functionality a bit. So, I will make necessary changes tomorrow and try to use the prepackaged Bitstream Vera fonts. Once again I'm sorry for the delay, regards, marek -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#295921: caudium: Caudium takes over from Apache
close 295921 thanks Marek Habersack said: Now that I'm thinking, maybe it's a bug in apt not in php4. Either way, I'll try to look closer into the issue and see where to assign the bug, This is quite obviously a bug in apt, see #297702 I'm closing this bug instead of reassigning it to apt since the issue is already reported for apt. thanks, marek signature.asc Description: Digital signature
Bug#295921: caudium: Caudium takes over from Apache
On Mon, Mar 07, 2005 at 11:37:17AM +0900, Adam Rice scribbled: This just happened to me too. I don't know why Caudium was installed, but the result was major suckage. This may not actually be a bug in Caudium, but in the depends for another package. But I was able to uninstall Caudium without difficultly, so frankly, I'm confused. It might be a bug in php4: % apt-cache show php4 ... Depends: libapache-mod-php4 (= 4:4.3.10-8) | libapache2-mod-php4 (= 4:4.3.10-8) | caudium-php4 (= 4:4.3.10-8), php4-common (= 4:4.3.10-8) ... So my guess is that for some weird reason the above pulls caudium-php4 and, in consequence, caudium. I'm also wondering whether caudium asked you about the port it should listen on - it should have done that precisely to avoid clash with any installed webserver. Now that I'm thinking, maybe it's a bug in apt not in php4. Either way, I'll try to look closer into the issue and see where to assign the bug, regards, marek signature.asc Description: Digital signature
Bug#292806: still bug in 0.9.2
On Sun, Feb 06, 2005 at 05:58:05PM -0500, Brenda J. Butler scribbled: Ok, so I saw the new email to this bug and downloaded the upstream 0.9.2 version and tried that. It still fails in cpu detection, this time the error message _is_ printed and it says: Error : cannot open '/home/bjb/.pmk/pmkcpu.dat' : No such file or directory. Error : failure in cpu detection. Error : child failed (status 256) Sorry for replying only now, I've been terribly busy lately. I've just built 0.9.2 and tested it on my machine - no segfault, no --compare-versions problem anymore. I will upload the package shortly, please test and if you still see the problem, reopen the bug. best regards, marek signature.asc Description: Digital signature
Bug#292440: pure-ftpd: Patch to set PAM_RHOST and PAM_RUSER for pam authentication
Package: pure-ftpd
Version: 1.0.19-4
Severity: important
Tags: patch
Hi,
The attached patch adds support for setting of two PAM items - PAM_RUSER
and PAM_RHOST (for remote user and host, respectively). This is needed to
be able to use pam_access with pure-ftpd for non-local login setups. The
changes are simple and don't affect much code, please consider applying it.
thanks,
marek
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-ac10-tux3a7-hacks
Locale: LANG=en_US.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Versions of packages pure-ftpd depends on:
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
ii libcap1 1:1.10-14support for getting/setting POSIX.
ii libpam0g0.76-22 Pluggable Authentication Modules l
ii libssl0.9.7 0.9.7e-3 SSL shared libraries
ii pure-ftpd-common1.0.19-4 Pure-FTPd FTP server (Common Files
-- no debconf information
--- pure-ftpd-1.0.19.orig/src/log_pam.c
+++ pure-ftpd-1.0.19/src/log_pam.c
@@ -135,7 +135,11 @@
int pam_error;
struct passwd pw, *pw_;
char *dir = NULL;
-
+#ifdef PAM_RHOST
+struct hostent *hent;
+const char *host;
+#endif
+
(void) sa;
(void) peer;
result-auth_ok = 0;
@@ -143,6 +147,31 @@
PAM_username = user;
pam_error = pam_start(pure-ftpd, user, PAM_conversation, pamh);
PAM_BAIL;
+
+/* set PAM_RUSER and PAM_RHOST for modules like pam_env or pam_access */
+#ifdef PAM_RHOST
+logfile(LOG_INFO, PAM_RHOST enabled. Getting the peer address);
+switch (STORAGE_FAMILY(*peer)) {
+ case AF_INET:
+hent = gethostbyaddr(STORAGE_SIN_ADDR(*peer), sizeof(STORAGE_SIN_ADDR(*peer)), AF_INET);
+ break;
+
+ case AF_INET6:
+hent = gethostbyaddr(STORAGE_SIN_ADDR6(*peer), sizeof(STORAGE_SIN_ADDR6(*peer)), AF_INET6);
+ break;
+}
+
+if (!hent)
+ (void)pam_set_item(pamh, PAM_RHOST, NULL);
+else
+ (void)pam_set_item(pamh, PAM_RHOST, hent-h_name);
+#endif
+
+
+#ifdef PAM_RUSER
+(void)pam_set_item(pamh, PAM_RUSER, user);
+#endif
+
# ifdef PAM_TTY
(void) pam_set_item(pamh, PAM_TTY, pure-ftpd);
# endif
