Accepted xcalendar-i18n 4.0.0.i18p1-14 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 26 Jul 2006 03:09:50 +0900 Source: xcalendar-i18n Binary: xcalendar-i18n Architecture: source i386 Version: 4.0.0.i18p1-14 Distribution: unstable Urgency: low Maintainer: Taketoshi Sano [EMAIL PROTECTED] Changed-By: Taketoshi Sano [EMAIL PROTECTED] Description: xcalendar-i18n - calendar program on X with i18n support Closes: 346794 364512 376403 Changes: xcalendar-i18n (4.0.0.i18p1-14) unstable; urgency=low . * a little modification based on 13.2 Thanks for Luk Claes. (Closes: #346794, #376403, #364512) * remove x-dev from build-depends because x-dev is a dummy package to depend on x11proto-core-dev, and libxt-dev in build-depends already depends on x11proto-core-dev. * switch debhelper V5 from old V1 (debian/rules has changed) * Bump to Standards-Version 3.7.2 from 3.5.9 Files: bdeb897394c267a9fd8fb143181a6ee3 670 x11 extra xcalendar-i18n_4.0.0.i18p1-14.dsc 5f2bf8d1ce488422774f11d99ef08f41 12618 x11 extra xcalendar-i18n_4.0.0.i18p1-14.diff.gz 789820ea4681ab64ef5130b1060660cd 33504 x11 extra xcalendar-i18n_4.0.0.i18p1-14_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFExmKo0LPz0K4xwAkRAuREAJsGRl37hpkMjLwyZa62hheya6pAbwCcCHOF VMV5EUKLNd+QWDDjsV/GzS0= =MTJY -END PGP SIGNATURE- Accepted: xcalendar-i18n_4.0.0.i18p1-14.diff.gz to pool/main/x/xcalendar-i18n/xcalendar-i18n_4.0.0.i18p1-14.diff.gz xcalendar-i18n_4.0.0.i18p1-14.dsc to pool/main/x/xcalendar-i18n/xcalendar-i18n_4.0.0.i18p1-14.dsc xcalendar-i18n_4.0.0.i18p1-14_i386.deb to pool/main/x/xcalendar-i18n/xcalendar-i18n_4.0.0.i18p1-14_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted asclassic 1.1b-29 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 26 Jul 2006 04:03:32 +0900 Source: asclassic Binary: asclassic Architecture: source i386 Version: 1.1b-29 Distribution: unstable Urgency: low Maintainer: Taketoshi Sano [EMAIL PROTECTED] Changed-By: Taketoshi Sano [EMAIL PROTECTED] Description: asclassic - X11 window manager, AfterStep Classic (forked from v1.1) Closes: 346652 350782 366831 Changes: asclassic (1.1b-29) unstable; urgency=low . * Rebuild based on 1.1b-28.3 Thanks to Luk Claes and Matej Vela. (Closes: #346652, #350782, #366831) * Bump to Standards-Version 3.7.2 from 3.6.1 * switch debhelper V5 from V2 Files: 5e606542c64fd710d3b6fb0e185cabcf 638 x11 optional asclassic_1.1b-29.dsc b8966c38c9244b0971b480014f74f03f 77999 x11 optional asclassic_1.1b-29.diff.gz 3482f1141d148affed6cea5911f2b9d9 532822 x11 optional asclassic_1.1b-29_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFExnVD0LPz0K4xwAkRAojNAKCX/5hsdkXZVAhwdfD/yFs72kWczgCeINf8 RDF4rxmc8Yoc/dayfw3ei7M= =ffnW -END PGP SIGNATURE- Accepted: asclassic_1.1b-29.diff.gz to pool/main/a/asclassic/asclassic_1.1b-29.diff.gz asclassic_1.1b-29.dsc to pool/main/a/asclassic/asclassic_1.1b-29.dsc asclassic_1.1b-29_i386.deb to pool/main/a/asclassic/asclassic_1.1b-29_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fdclone 2.06c-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 19 Mar 2005 20:48:35 +0900 Source: fdclone Binary: fdclone Architecture: source i386 Version: 2.06c-1 Distribution: unstable Urgency: low Maintainer: Taketoshi Sano [EMAIL PROTECTED] Changed-By: Taketoshi Sano [EMAIL PROTECTED] Description: fdclone- A console-base lightweight file manager Changes: fdclone (2.06c-1) unstable; urgency=low . * New upstream release Files: 695f5bfee6e38ea8f9cd89007a7806f8 578 shells optional fdclone_2.06c-1.dsc d3b14aedfb01aa8320e4d0dadd0def66 670527 shells optional fdclone_2.06c.orig.tar.gz b03703fcda23ce9ba169ad212e5a2dde 18879 shells optional fdclone_2.06c-1.diff.gz 9743f80508fde3a501d39feab2b57526 430736 shells optional fdclone_2.06c-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCRHEE0LPz0K4xwAkRAj0xAJ0Z0sd23pdowZuwQl1SrOY3WtCsQACglipL ydWa68lJBhxhSRXCofFopDQ= =RpXa -END PGP SIGNATURE- Accepted: fdclone_2.06c-1.diff.gz to pool/main/f/fdclone/fdclone_2.06c-1.diff.gz fdclone_2.06c-1.dsc to pool/main/f/fdclone/fdclone_2.06c-1.dsc fdclone_2.06c-1_i386.deb to pool/main/f/fdclone/fdclone_2.06c-1_i386.deb fdclone_2.06c.orig.tar.gz to pool/main/f/fdclone/fdclone_2.06c.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted tcltk8.0-ja 8.0.4jp1.3-15 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 19 Mar 2005 07:41:46 +0900 Source: tcltk8.0-ja Binary: tk8.0-ja tcl8.0-ja Architecture: source i386 Version: 8.0.4jp1.3-15 Distribution: unstable Urgency: low Maintainer: Taketoshi Sano [EMAIL PROTECTED] Changed-By: Taketoshi Sano [EMAIL PROTECTED] Description: tcl8.0-ja - Japanese localized version of tcl 8.0 tk8.0-ja - Japanese localized version of Tk 8.0 Closes: 297045 297837 Changes: tcltk8.0-ja (8.0.4jp1.3-15) unstable; urgency=low . * add LD_LIBRARY_PATH for dpkg-shlibdeps, and debian/shlibs.local. (Closes: #297045) * add patch from Andreas Jochens [EMAIL PROTECTED]. (Closes: #297837) * move scripts directories from /usr/lib to /usr/share (FHS) * update standard version. Files: 249ba99e0d2f6d702bdc51c563259ff2 636 oldlibs extra tcltk8.0-ja_8.0.4jp1.3-15.dsc 89d49dfd4a851a892f9d6dac643e01bd 62930 oldlibs extra tcltk8.0-ja_8.0.4jp1.3-15.diff.gz ca618e5d58919f86cbe937627707ffcf 344358 oldlibs extra tcl8.0-ja_8.0.4jp1.3-15_i386.deb a0d21879b3f370926fdf0d89003122e6 736136 oldlibs extra tk8.0-ja_8.0.4jp1.3-15_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCO3X20LPz0K4xwAkRAmu2AJ99w9ZMPFa6TbR9trNtYRXtFOvR0QCfSD8U fM/R8vD066aFb0Qlh1p29VY= =ZDnz -END PGP SIGNATURE- Accepted: tcl8.0-ja_8.0.4jp1.3-15_i386.deb to pool/main/t/tcltk8.0-ja/tcl8.0-ja_8.0.4jp1.3-15_i386.deb tcltk8.0-ja_8.0.4jp1.3-15.diff.gz to pool/main/t/tcltk8.0-ja/tcltk8.0-ja_8.0.4jp1.3-15.diff.gz tcltk8.0-ja_8.0.4jp1.3-15.dsc to pool/main/t/tcltk8.0-ja/tcltk8.0-ja_8.0.4jp1.3-15.dsc tk8.0-ja_8.0.4jp1.3-15_i386.deb to pool/main/t/tcltk8.0-ja/tk8.0-ja_8.0.4jp1.3-15_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted extipl 5.04-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 9 Mar 2005 21:14:01 +0900 Source: extipl Binary: extipl extipl-boot Architecture: source i386 Version: 5.04-2 Distribution: unstable Urgency: low Maintainer: Taketoshi Sano [EMAIL PROTECTED] Changed-By: Taketoshi Sano [EMAIL PROTECTED] Description: extipl - Yet Another Boot Selector for IBM-PC compatibles extipl-boot - ExtIPL, an enhanced boot code (IPL) for IBM-PC Closes: 250086 Changes: extipl (5.04-2) unstable; urgency=low . * Add amd64 to Architecture field in the control file. I don't know if this work on amd64. But users should have known it better than me. (Closes: #250086) Files: 1e70ca5b0c1a361cfbb0a8c1f67562a0 567 admin optional extipl_5.04-2.dsc a5ed1f571bafdb4f4fb6f4db002e987a 4396 admin optional extipl_5.04-2.diff.gz f5d30bbbcfee33948c079f1fbeb43e30 68562 admin optional extipl_5.04-2_i386.deb 6b3af40beead20287fbcfefc9654cfe4 13218 admin optional extipl-boot_5.04-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCLvMv0LPz0K4xwAkRAiOIAKCmJ4GHLvUGaJdG8qR6R70IdxSNEQCfQGUB 5Hta7C4e8WZYE4/wTqVD6vk= =VkpN -END PGP SIGNATURE- Accepted: extipl-boot_5.04-2_i386.deb to pool/main/e/extipl/extipl-boot_5.04-2_i386.deb extipl_5.04-2.diff.gz to pool/main/e/extipl/extipl_5.04-2.diff.gz extipl_5.04-2.dsc to pool/main/e/extipl/extipl_5.04-2.dsc extipl_5.04-2_i386.deb to pool/main/e/extipl/extipl_5.04-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted asclassic 1.1b-27 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 9 Mar 2005 22:40:52 +0900 Source: asclassic Binary: asclassic Architecture: source i386 Version: 1.1b-27 Distribution: unstable Urgency: low Maintainer: Taketoshi Sano [EMAIL PROTECTED] Changed-By: Taketoshi Sano [EMAIL PROTECTED] Description: asclassic - X11 window manager, AfterStep Classic (forked from v1.1) Closes: 136689 296931 Changes: asclassic (1.1b-27) unstable; urgency=low . * stop using wm-menu-config from postinst/postrm (Closes: #296931) * move files for backgrounds from /usr/share/backgrounds to /usr/share/wallpapers (Closes: #136689) Files: 77434feef37bae0585d67f8a09c6dfe6 584 x11 optional asclassic_1.1b-27.dsc 33343f862c90384400f57d747bfebe98 77467 x11 optional asclassic_1.1b-27.diff.gz 31fd13d07545299faf9e592c8d6814c0 528452 x11 optional asclassic_1.1b-27_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCLxb10LPz0K4xwAkRAhPVAJ9gp101sQssqAMXtRbW9zX1mFUJqACgup2F PC+vQnZ52nkbsDgPhp880RM= =g2FZ -END PGP SIGNATURE- Accepted: asclassic_1.1b-27.diff.gz to pool/main/a/asclassic/asclassic_1.1b-27.diff.gz asclassic_1.1b-27.dsc to pool/main/a/asclassic/asclassic_1.1b-27.dsc asclassic_1.1b-27_i386.deb to pool/main/a/asclassic/asclassic_1.1b-27_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted asclassic 1.1b-28 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 10 Mar 2005 06:34:17 +0900 Source: asclassic Binary: asclassic Architecture: source i386 Version: 1.1b-28 Distribution: unstable Urgency: low Maintainer: Taketoshi Sano [EMAIL PROTECTED] Changed-By: Taketoshi Sano [EMAIL PROTECTED] Description: asclassic - X11 window manager, AfterStep Classic (forked from v1.1) Changes: asclassic (1.1b-28) unstable; urgency=low . * update sample.steprc to migration of modules from /usr/X11R6/lib/asclassic/ to /usr/lib/asclassic/ * update postist/prerm as above (update-alternatives) * comment out pine and netscape from sample Wharf configuration, and add xman. Files: bca8532182ed48e4a6f4fee06baaef17 584 x11 optional asclassic_1.1b-28.dsc fd1896ad1070c9273251f597805df10a 77577 x11 optional asclassic_1.1b-28.diff.gz 24387bbd9ebfda4dae95400bf6eeb5d1 528608 x11 optional asclassic_1.1b-28_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCL2y00LPz0K4xwAkRArsrAJ4xLNNGxrqTnd8HfakXfnCaTNWElgCfXuwu Gk5AV/qXjrlsmL6Wtj06DdM= =E3IB -END PGP SIGNATURE- Accepted: asclassic_1.1b-28.diff.gz to pool/main/a/asclassic/asclassic_1.1b-28.diff.gz asclassic_1.1b-28.dsc to pool/main/a/asclassic/asclassic_1.1b-28.dsc asclassic_1.1b-28_i386.deb to pool/main/a/asclassic/asclassic_1.1b-28_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gsfonts-wadalab 0.20010409-7 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 8 Mar 2005 21:54:03 +0900 Source: gsfonts-wadalab Binary: gsfonts-wadalab-common gsfonts-wadalab-mincho gsfonts-wadalab-gothic Architecture: source all Version: 0.20010409-7 Distribution: unstable Urgency: low Maintainer: Taketoshi Sano [EMAIL PROTECTED] Changed-By: Taketoshi Sano [EMAIL PROTECTED] Description: gsfonts-wadalab-common - Japanese symbol fonts for the ghostscript interpreter gsfonts-wadalab-gothic - Japanese gothic fonts for the ghostscript interpreter gsfonts-wadalab-mincho - Japanese mincho fonts for the ghostscript interpreter Closes: 270652 Changes: gsfonts-wadalab (0.20010409-7) unstable; urgency=low . * Apply patch from Andreas Jochen (Closes: #270652) * Change the check code for root ($$EUID - $$UID), I don't know if this can solve the problem in #266381, but anyway try this. (dh_testroot uses $, and it means $UID according to manpage.) Files: 89fe5bec679d7194cd8db7a98e2afe69 657 text extra gsfonts-wadalab_0.20010409-7.dsc 4ccfe2442a0b216b8ce1e897483e7498 16549 text extra gsfonts-wadalab_0.20010409-7.diff.gz 5b82913ffbf0e54be836beca1584a6b3 82268 text extra gsfonts-wadalab-common_0.20010409-7_all.deb 2b5b1fc798da2825d4c8a7f98eafcdc0 3772626 text extra gsfonts-wadalab-mincho_0.20010409-7_all.deb 503436b3383f8b4f153f0bbe0db3d163 2437172 text extra gsfonts-wadalab-gothic_0.20010409-7_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCLacX0LPz0K4xwAkRAvjAAJwPC85SkZ6pW1mJe+hvEK0Sr9aZoACfUZiH ISCUX9Ilo5ucZkz1hIBqADY= =Vmv5 -END PGP SIGNATURE- Accepted: gsfonts-wadalab-common_0.20010409-7_all.deb to pool/main/g/gsfonts-wadalab/gsfonts-wadalab-common_0.20010409-7_all.deb gsfonts-wadalab-gothic_0.20010409-7_all.deb to pool/main/g/gsfonts-wadalab/gsfonts-wadalab-gothic_0.20010409-7_all.deb gsfonts-wadalab-mincho_0.20010409-7_all.deb to pool/main/g/gsfonts-wadalab/gsfonts-wadalab-mincho_0.20010409-7_all.deb gsfonts-wadalab_0.20010409-7.diff.gz to pool/main/g/gsfonts-wadalab/gsfonts-wadalab_0.20010409-7.diff.gz gsfonts-wadalab_0.20010409-7.dsc to pool/main/g/gsfonts-wadalab/gsfonts-wadalab_0.20010409-7.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fdclone 2.04a-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 9 Aug 2003 09:58:31 +0900 Source: fdclone Binary: fdclone Architecture: source i386 Version: 2.04a-1 Distribution: unstable Urgency: low Maintainer: Taketoshi Sano [EMAIL PROTECTED] Changed-By: Taketoshi Sano [EMAIL PROTECTED] Description: fdclone- A console-base lightweight file manager Changes: fdclone (2.04a-1) unstable; urgency=low . * New upstream release * update debian/watch. now I can use uscan command. :) Files: 58db0c91c41016b47b94fce604c50193 567 shells optional fdclone_2.04a-1.dsc 9c488dec8e6e8236c5631efd5dd89f8c 641863 shells optional fdclone_2.04a.orig.tar.gz 5dcae526594de00d7eff24c6452b4954 16778 shells optional fdclone_2.04a-1.diff.gz 9434d9667afa423222c1678455adc97b 400494 shells optional fdclone_2.04a-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/NE960LPz0K4xwAkRAoJeAJ4s3oD6Pq9dQOuXzfAovrk40+GRpQCbBlbS 1tgR+1g1DjySlm/ohdjNoxE= =CFfV -END PGP SIGNATURE- Accepted: fdclone_2.04a-1.diff.gz to pool/main/f/fdclone/fdclone_2.04a-1.diff.gz fdclone_2.04a-1.dsc to pool/main/f/fdclone/fdclone_2.04a-1.dsc fdclone_2.04a-1_i386.deb to pool/main/f/fdclone/fdclone_2.04a-1_i386.deb fdclone_2.04a.orig.tar.gz to pool/main/f/fdclone/fdclone_2.04a.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fdclone 2.04-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 26 Jun 2003 23:04:42 +0900 Source: fdclone Binary: fdclone Architecture: source i386 Version: 2.04-1 Distribution: unstable Urgency: low Maintainer: Taketoshi Sano [EMAIL PROTECTED] Changed-By: Taketoshi Sano [EMAIL PROTECTED] Description: fdclone- A console-base lightweight file manager Changes: fdclone (2.04-1) unstable; urgency=low . * New upstream release Files: f891853b3c6401dfffa0b4e2b98e0c18 565 shells optional fdclone_2.04-1.dsc eaae4b005df484de36314c0703b6ecb7 641100 shells optional fdclone_2.04.orig.tar.gz 37a406fc2ced35a96e75dcefdae63e9b 16753 shells optional fdclone_2.04-1.diff.gz e33f138fcd5c2fb1546d46f834d1a6d0 400058 shells optional fdclone_2.04-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/AD880LPz0K4xwAkRAiRMAJ9LRENVPqFEeoLcegABezG+goXt4QCeJHSY vpyNSyOah+7NTzNU28tE1ds= =WfMq -END PGP SIGNATURE- Accepted: fdclone_2.04-1.diff.gz to pool/main/f/fdclone/fdclone_2.04-1.diff.gz fdclone_2.04-1.dsc to pool/main/f/fdclone/fdclone_2.04-1.dsc fdclone_2.04-1_i386.deb to pool/main/f/fdclone/fdclone_2.04-1_i386.deb fdclone_2.04.orig.tar.gz to pool/main/f/fdclone/fdclone_2.04.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted forutil 0.62-4 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 7 Jun 2003 11:24:53 +0900 Source: forutil Binary: forutil Architecture: source i386 Version: 0.62-4 Distribution: unstable Urgency: low Maintainer: Taketoshi Sano [EMAIL PROTECTED] Changed-By: Taketoshi Sano [EMAIL PROTECTED] Description: forutil- a collection of FORTRAN 77 utilities Changes: forutil (0.62-4) unstable; urgency=low . * update build-depends from libgdbmg1-dev to libgdbm-dev (Thanks to the maintainer of libgdbm for his announcement) Files: a6c5596650aeef4efaf5a280013dbd40 585 devel extra forutil_0.62-4.dsc 93fb0c9e6f4d62c3e369728f06d5674f 35006 devel extra forutil_0.62-4.diff.gz b053e9151c84375e8144c593f6d28477 76050 devel extra forutil_0.62-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+4VSC0LPz0K4xwAkRAnuFAJ464POwMO0vlyeGWwKr/BILidQX4ACePPGO SocOTs2/l/YumCnTwapFIME= =0xEg -END PGP SIGNATURE- Accepted: forutil_0.62-4.diff.gz to pool/main/f/forutil/forutil_0.62-4.diff.gz forutil_0.62-4.dsc to pool/main/f/forutil/forutil_0.62-4.dsc forutil_0.62-4_i386.deb to pool/main/f/forutil/forutil_0.62-4_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fdclone 2.02a-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 31 Dec 2002 19:56:36 +0900 Source: fdclone Binary: fdclone Architecture: source i386 Version: 2.02a-1 Distribution: unstable Urgency: low Maintainer: Taketoshi Sano [EMAIL PROTECTED] Changed-By: Taketoshi Sano [EMAIL PROTECTED] Description: fdclone- A console-base lightweight file manager Closes: 174592 Changes: fdclone (2.02a-1) unstable; urgency=low . * New upstream release (Closes: #174592) Files: 0da0a86478babd8c737d9744f0dd5ff5 567 shells optional fdclone_2.02a-1.dsc 8a20667ed0abce1809c15e2f2a210518 581052 shells optional fdclone_2.02a.orig.tar.gz 1f020530ba191c9ce28ee0271793a80d 14911 shells optional fdclone_2.02a-1.diff.gz 05aac0482fd8d457f4bdee56bfec3a18 370536 shells optional fdclone_2.02a-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+EZ9S0LPz0K4xwAkRAqyFAKCQFcE+7QG9FaK9TKiASj4WWKGzYACcDhxe FJ8ZYNCZEn4WmtASB0QjhGU= =XFca -END PGP SIGNATURE- Accepted: fdclone_2.02a-1.diff.gz to pool/main/f/fdclone/fdclone_2.02a-1.diff.gz fdclone_2.02a-1.dsc to pool/main/f/fdclone/fdclone_2.02a-1.dsc fdclone_2.02a-1_i386.deb to pool/main/f/fdclone/fdclone_2.02a-1_i386.deb fdclone_2.02a.orig.tar.gz to pool/main/f/fdclone/fdclone_2.02a.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: test -d /usr/man mail submit@bugs
Hi. In [EMAIL PROTECTED], on Fri, 29 Dec 2000 01:50:36 +1100, on Re: test -d /usr/man mail [EMAIL PROTECTED], Hamish Moffatt [EMAIL PROTECTED] wrote: On Thu, Dec 28, 2000 at 09:13:32AM -0500, Chad Miller wrote: I noticed that the FHS2.1 doesn't have /usr/man -- only /usr/share/man. On this box, there are... [...] ...several packages that install stuff in /usr/man . Do these warrant bug reports? Yep, IMHO. We should be FHS compliant by now, there's been plenty of time. The CTTE recommendation, or DPL order, was that the woody has the symlinks from /usr/man/pakcage to /usr/share/man/package, IIRC. Is this changed now ? Can we drop the postinst/prerm requirements to create/remove those symlinks ? -- Taketoshi Sano: [EMAIL PROTECTED],[EMAIL PROTECTED],[EMAIL PROTECTED]
Re: test -d /usr/man mail submit@bugs
Clearly, I was confused. excuse me. Matt Zimmerman [EMAIL PROTECTED] wrote: /usr/man and /usr/share/man don't have package directories, only man sections (e.g. man[1-8]). I think you are confusing /usr/man and /usr/doc. Hamish Moffatt [EMAIL PROTECTED] wrote: I think you mean /usr/doc. No symlinks are needed for /usr/man. OK, I see now. Thanks. :) -- Taketoshi Sano: [EMAIL PROTECTED],[EMAIL PROTECTED],[EMAIL PROTECTED]
Re: X 4 and app-defaults
Hi. In [EMAIL PROTECTED], on Wed, 27 Dec 2000 12:27:43 +0100, on Re: X 4 and app-defaults, Bernd Eckenfels [EMAIL PROTECTED] wrote: what about localisation of app-default, I see XEarth ships with # ls /etc/X11/*/app-defaults/XEarth /etc/X11/ja_JP.eucJP/app-defaults/XEarth /etc/X11/ko_KR.eucKR/app-defaults/XEarth I would prefer /etc/X11/app-defaults/locale/Class as man is doing. Well, traditional X11 handling requires the location of XLIBDIR(/usr/X11R6/lib/X11 for potato)/locale/app-defaults/, so the new location /etc/X11/locale/app-defaults/ is just following that traditional way. And this behavior has already submitted as the patch by M. Ishikawa, and Branden kindly used it months ago. I can't get what is the merit of your proposal, but maybe this should be decided at the upstream level (i.e., xfree86 in this case, or TOG) I think. Regards. -- Taketoshi Sano: [EMAIL PROTECTED],[EMAIL PROTECTED],[EMAIL PROTECTED]
Re: priority of x-window-manager
Seconded, heartily. Branden Robinson [EMAIL PROTECTED] writes: To sum up, what I'm saying is this: I think a Debian window manager policy should say that window managers should be given higher priority if they DON'T mangle localized information that they are intended to pass along to the user. And that is what I understand internationalization of computer software to mean -- it makes localization transparent and possible. -- Taketoshi Sano: [EMAIL PROTECTED],[EMAIL PROTECTED],[EMAIL PROTECTED]
Re: priority of x-window-manager
Hi. Branden Robinson [EMAIL PROTECTED] writes: On Wed, Mar 15, 2000 at 09:04:47PM +0900, Changwoo Ryu wrote: Korean (and maybe Japanese) X users often see the Netscape titlebar incorrectly displays Korean web page title. Many of the window managers still don't care about this and just draw the raw string with XDrawString(). The correct behavior is decoding the received compound strings and drawing the decoded ones with XmbDrawString(). I'm willing to support such a priority increase now; but first, please come up with a list of specific things that a window manager needs to do. Thank you Branden, and Changwoo. I am happy to read this. We can't just say add 10 points if the window manager is internationalized without telling the possible thick-headed American package maintainer how to determine whether it is or not. :) I have thought that users can judge if the specific software is correctly internationalized or not, and they will file their report on BTS if they find the wrong priorities. But your concern may be reasonable. One item would obviously be: + The window manager should use XmbDrawString() instead of XDrawString() for non-error/non-diagnostic text output. Please come up with more, if there are any, and I'd be happy to make a new policy proposal incorporating your suggestions. In fact, the true internationalization may require more than just replacing XDrawString() with XmbDrawString(), but this is a good indicator as a start point, I think. # Anyway, users will file their report on that package if it can not be used. Just one thing: Error text output could be localized one (libc does have localized error messages for such as No such file or directory or File exists. So excluding error output is not good in this case, I think. -- Taketoshi Sano: [EMAIL PROTECTED],[EMAIL PROTECTED],[EMAIL PROTECTED]
Re: Use https://db.debian.org/
Hi. In article [EMAIL PROTECTED], I wrote: Is it possible to add INPUT TYPE=reset value=reset button on the edit your info page ? Because I use Netscape Navigator to access encrpyted page currently, but it has some difficulties to handle the input form page. I have found last night that this has been already implemented. Thank you ! Or please tell me the other browser which can be used to access there with encryption enabled (free one is best, but I don't know). Thanks. And Raul kindly informed me of linx-ssl. I can connect https://db.debian.org/ using it via dial-up ppp from my home. :) just FYI. -- Taketoshi Sano: [EMAIL PROTECTED],[EMAIL PROTECTED],[EMAIL PROTECTED]
Re: sash
Hi. In article [EMAIL PROTECTED] [EMAIL PROTECTED] (Raul Miller) writes: I've filed a wishlist bug against the passwd package to have sash included. [If you've also done this, let me know the bug number so I can merge them?] I have not done, and will not because I knew you already did it :) Thanks for your consideration to my proposal. -- Taketoshi Sano: [EMAIL PROTECTED],[EMAIL PROTECTED],[EMAIL PROTECTED]
Re: Use https://db.debian.org/ [was Re: Add your location ...]
Hi. In article [EMAIL PROTECTED] [EMAIL PROTECTED] (Jason Gunthorpe) writes: On Wed, 22 Sep 1999, James A. Treacy wrote: I should have used https://www.debian.org/ in the original mail. Sorry. Everyone who can (legally) use ssl should use that URL. Yes, this is definately the best way to enter the data right now. Encrypted LDAP is comming in many months though. Is it possible to add INPUT TYPE=reset value=reset button on the edit your info page ? Because I use Netscape Navigator to access encrpyted page currently, but it has some difficulties to handle the input form page. Or please tell me the other browser which can be used to access there with encryption enabled (free one is best, but I don't know). Thanks. -- Taketoshi Sano: [EMAIL PROTECTED],[EMAIL PROTECTED],[EMAIL PROTECTED]
Re: i dont understand something or dpkg is simply buggy
Hi. In article [EMAIL PROTECTED] [EMAIL PROTECTED] (Vincent Danjean) writes: I've a similar problem. I use Debian-ja and I've the folowing things : Package: 2utf Recommends: man-db (= 2.3.10-37) Package: man-db Status: deinstall ok config-files Version: 2.3.10-69i Replaces: man Provides: man Conflicts: man Package: man-db-ja Status: install ok installed Version: 2.3.10-69f.jp0.1 Replaces: man Provides: man Conflicts: man As 2utf only recommends I can force dselect to accept this selection. Should I fill a bug report against 2utf ? I'm not sure because man-db-ja is not (yet) in Debian (it is in Debian-ja). You don't need to file a bug report against anyone. Now Fabrizio Polacco, the maintainer of man-db, plans to enhance his package to support manpages written in Japanese. Since he already posted about his modification on debian-i18n@lists.debian.org, and we tested it and followd some requests for it, I hope we will not need man-db-ja soon. I have tested his patch with my modification on my slink system as well as on potato, by locally building patched package. The problem related to version-depends, is one of main reasons that we need JP Merge Operation, since separate packaging would not solve this easily. You can find some more samples in JP Packages. We hope that the coming potato has many enhanced support for our language by helping and efforts from many official maintainers in Debian. Thanks to you. (my current targets are man-db, gs, and sgml-tools. but maybe I should contribute to the work for boot-floppies after) -- Taketoshi Sano: [EMAIL PROTECTED],[EMAIL PROTECTED],[EMAIL PROTECTED]
Re: i dont understand something or dpkg is simply buggy
Hi. In article [EMAIL PROTECTED] [EMAIL PROTECTED] (Fumitoshi UKAI) writes: We are now trying to merge man-db-ja features to man-db cooperated with Fabrizio Polacco [EMAIL PROTECTED], so man-db-ja will not be removed soon. err. I think that UKAI has wished to write here so man-db-ja will be removed soon. We are looking forward to new man-db coming with Japanese support :) -- Taketoshi Sano: [EMAIL PROTECTED],[EMAIL PROTECTED],[EMAIL PROTECTED]
Re: sash
Hi. In article [EMAIL PROTECTED] [EMAIL PROTECTED] (Raul Miller) writes: I think you should just use useradd to edit the password file. You mean without ensuring that the password is useful? I've already elected to give the admin a choice (whether or not to add the account -- that'll be in the next release). The problem with password prompting is that it doesn't fit well into an automated or gui install. Under these circumstances do you still feel it's useful to add a locked account? How about to include following small script (maybe /sbin/sashpasswd with permission 0700 or 0744): #! /bin/sh PATH=/usr/bin passwd root passwd sashroot and promote to use it instead of passwd command itself in changing the root's password. I think about hacking the passwd command, but it may go difficult work as the passwd package has so many patches, and not so efficient work to hack with other package, at least for me, I feel. It may be better just to use it. You wrote: | Ok, I'll put back a single install time question where the sysadmin has | one of several options: sash is inert and doesn't manage the password | file, sash will become the root shell, sash will create a sashroot | account from the current root account and use that as it's shell. | | And some notes on how to change this. then, the action maybe a) sash is inert and doesn't manage the password file. : only put the files into their place. b) sash will become the root shell. : a) + use usermod -s /bin/sash root or chsh -s /bin/sash root c) sash will create a sashroot account from the current root account and use that as it's shell. : the default setting for 3.3-6 and (here is my proposal) d) sash will create a locked sashroot account with useradd, and display the message to use sashpasswd above as soon as possible. By the way, /bin/sash is not listed on /etc/shells. Is it Okay ? # sash may be not the choise for ordinary users, but it does not # need to prohibit to use sash as login shell by normal users. ## Well, I should file this to passwd package as wishlist,,, Thanks. -- Taketoshi Sano: [EMAIL PROTECTED],[EMAIL PROTECTED],[EMAIL PROTECTED]
Re: Packages for adoption
Hi. I am now using and prefer the asclassic, and since knghtbrd (the maintainer) and joel (he is another applicant for asclassic) agreed to my succession, I take it over. Thanks. In article [EMAIL PROTECTED] [EMAIL PROTECTED] (Joseph Carter) writes: [1 text/plain; us-ascii (quoted-printable)] I have a few packages which are mine that I no longer actually use and it would be best to give these to other developers who WOULD use them: asclassic - version 1.1 of AfterStep, up until recently the only wm I could stomach. The others all sucked, including new versions of AS which were painful to configure, poorly documented, and too damned slow. Window Maker has become at least as useful to me and in fact I think I have fewer complaints about wmaker than asclassic at this point. -- Taketoshi Sano: [EMAIL PROTECTED],[EMAIL PROTECTED],[EMAIL PROTECTED]
Re: extipl, mbr--why? (was: GRUB)
Hi. In article [EMAIL PROTECTED] [EMAIL PROTECTED] (Philip Hands) writes: Andrew Pimlott [EMAIL PROTECTED] writes: (snip) May I ask what the point of these enhanced mbr's is, since all of these features are available from the boot loader (eg LILO)? I've always had my LILO configured to boot from the floppy and alternate partitions, and this would be fairly easy to add to the default lilo.conf for beginners. Maybe you are so clever that you can easily understand how to fiddle that lilo.conf, but there are many people who can not find proper settings of lilo for their needs. (So both of how-to and FAQ about lilo is distributed additional to the very detailed documents of lilo itself) And LILO require the files (at least the 2nd loader and map file) on different place than the MBR (Master Boot Record). you can boot from alternate partitions by your setup, but if you remove the partition which includes the required files (2nd loader and kernel map) and overwrite on them, the rest partition would not work for you. By putting the current mbr or alternate extipl on MBR, you can select partitions by solely using the code in MBR (just 446bytes). And you can set lilo in each partitions boot sector, this is more easy configuration than having multiple partition setup in single lilo.conf for many beginners. No beginner understands what those funny letters that mbr prints mean anyway, and I'm sure I'm not the only one who gets annoyed when they pop up because I'm holding down shift to get the LILO prompt. Why don't you put delay=30 or delay=20 in your lilo.conf ? It makes more easy to catch the LILO prompt for you. What was the rationale for adding mbr to the default configuration? To stop the annoying FAQ: Yes. Philip knows the begginers. These FAQ is very frequently up even these days, or much more since more and more people begin to use Linux and LILO. I think Debian's current configuration to use it's mbr package is reasonable. (Well, if I don't think so, I would not make the package of extipl :) just FYI. -- Taketoshi Sano: [EMAIL PROTECTED]
Re: debian-upload-queue in Japan
Hi! Josip Rodin [EMAIL PROTECTED] writes: Hm... it would be valid, but no one would find it aesthetically correct :) But this is all not really important, it's just a string in a config file. Thank you for your comment :) I see. Other members in JP project told me their ideas: i.e. hinokuni, sukiyaki, karate, kiai, hiyoko, far_east, kyokutoh, wabisabi, wasabi,,, If it is not really important, I prefer wasabi as the nickname. -- Taketoshi Sano: [EMAIL PROTECTED]
Re: Homapages in list of maintainers
Are there any objections for Ukai's taking charge of New Maintainers Interview in Japan ? If not, Please tell me the address to contact about this. Is [EMAIL PROTECTED] the correct address to contact ? In article [EMAIL PROTECTED] Taketoshi Sano [EMAIL PROTECTED] (me :) writes: Hi ! In article [EMAIL PROTECTED] Fumitoshi UKAI [EMAIL PROTECTED] writes: I can volunteer to do it, if it is really needed and anyone object to it. I've been maintain Debian JP machines, ftp archive, web server, mailing-list and Debian official mirror in Japan about two years or three. Thank you for your proposal :). I think it is required very much to get the Debian project to be more global organization as fast as we can, because if more people can join the project smoothly, the project can get more resource to do various task. if someone has the required condition to pass the verification by the New Maintainers Group, I can not find the merit of keep him (or her) in the long waiting queue. If the problem is only related to the human power, the action to do should be to increase the member of the Group, not to keep the queue longer. Adam Di Calro told Remember that approving new maintainer is a very _sensitive_ area, and I think it should be, but if the members in the Debian Project want to make this project to be true global and universal, an action to make the waiting queue shorter should be taken anyway now or in the near future. I am eager to know if anyone has objection. -- Taketoshi Sano: [EMAIL PROTECTED]
Re: debian-upload-queue in Japan
I got a mail of the idea just jp :) Thanks. It's most simple and clear, so I select this as my choice for the nickname of newly created dupload-queue. Any other opinions ? -- Taketoshi Sano: [EMAIL PROTECTED]
Re: debian-upload-queue in Japan
Thank you Josip :) In article [EMAIL PROTECTED] Josip Rodin [EMAIL PROTECTED] writes: On Fri, May 14, 1999 at 05:29:28AM +0900, Taketoshi Sano wrote: How is the other nicname chiark, elrangen, and giano named ? Are they named after the name of the location ? The machines had those names in their FQDNs, ftp.uni-erlangen.de, chiark.greenend.ac.uk, giano.com.dist.unige.it. uhm,,, the FQDN of the new upload-queue host is master.debian.or.jp,,, Do you feel that debian-jp is apropriate ? -- Taketoshi Sano: [EMAIL PROTECTED]
Re: debian-upload-queue in Japan (Re: Homapages in list of maintainers)
Thank you for your quick action :) In article [EMAIL PROTECTED] Fumitoshi UKAI [EMAIL PROTECTED] writes: I've already set up debian upload queue daemon on master.debian.or.jp. It seems to work fine, Susumu Osawa has uploaded aumix package as powerpc binary NMU via this upload queue yesterday:) Then we should inform [EMAIL PROTECTED] about this to make update the /etc/dupload.conf file, as Josip Rodin told here and me (Thank you Josip :). Now, I'm wondering what nickname is used for this upload queue. Since master-jp is already used for nickname to dupload for JP archives (in Debian JP Project), different name is better to distinguish, I think. Any idea? Even if the master-jp was not used, I think it is not suitable, because it resembles master. I don't like master-?? coming all over the world ;) How is the other nicname chiark, elrangen, and giano named ? Are they named after the name of the location ? I personally prefer sakura, a Cherry blossom, kind of flower. It is famous in Japan, as a gift from Japan to be planted along the Potomac(?) river in the Washington D.C. But another member of JP project said that name is used for another host which is used to build the sparc binary... Then, how about tokyo ? It is the name of a famous city that can be recognisable globally, I suppose. Or fuji ? the name of the highest mountain in Japan. -- Taketoshi Sano: [EMAIL PROTECTED]
Re: Homapages in list of maintainers
Hi. Thank you for your replies. I got relief to know this long waiting queue issue is rather common to all newcomers. In article [EMAIL PROTECTED] Adam Di Carlo [EMAIL PROTECTED] writes: Yes, well, it takes from 4 weeks to 6 months or longer for *all* people. I agree this should be shorter... Anyhow Debian-JP is *not* getting singled out. Everyone has this issue. I remeber the mail about 6 months waiting recently on this list. It's surely uncomfortable state which should be avoidable as much as we can. IF there's not way the guy can get a phone call, I'm afraid there's no way they can be confirmed and become a developer. Maybe he can get a call on holiday, I suppose. He is only afraid that he can't set time windows to new maitainers team, and he thought that the time of getting the call is unpredictable at all. According to James, all he says is it's unlikely to be between 8AM and 4PM British time on Monday-Friday. No one is asking you to sit by the phone for 3 months. But if you can only be reached at number XX-YYY at the hours of 3-7 GMT on Saturday, then tell the new maintainers that. Give them time windows that work for you. Give them a few different numbers and suggested times. I mean, common sense, people. Thanks for your information. That is what I want to know. Sure, but put people in the queue. It may take up to 3 months or longer if you're hard to reach on the phone -- so just plan on that. 3 months or longer ! (sigh) but if it is required condition, all we can do is just to wait in the queue ... Well, I think it's pretty clear that we need more active people in the New Maintainer Group. I hereby volunteer (I'm in the US, NYC area, and only speak English and smidgeons of Spanish, German, and French). I respect the people in the New Maintainer Group including you for their work. I hope there were the one in Japan, but no one can force the current official maintainer in JP to take charge of it,,, P.S. I think, and hope that the Debian is open project. It is -- don't get paranoid. The New Maintainer Group is just swamped a bit. I think it needs more people -- highly trustable people, of course. I hope the New Maintaier Group can find the highly trustable and active official maintainer as their member in Japan, or somewhere in the far-east area. -- Taketoshi Sano: [EMAIL PROTECTED]
Re: Homapages in list of maintainers
Thank you for your reply. I'm impressed your idea. In article [EMAIL PROTECTED] John Lapeyre [EMAIL PROTECTED] writes: I think it would be great for Debian JP and Debian to find someone in Japan who can do interviews in Japan and report to the new-maintainer people in Debian proper (in Europe or U.S.) That is to say, it would be good to have a new-maintainer person located in Japan. I think so. and more, I hope that the site for dupload established in Japan so that we can select the near site to upload our packages. In current standard /etc/dupload.conf contains chiark (uk), master (us?), erlangen (de), and giano (it). I hope that one of the JP's site is registered as the official upload site. But it may takes some effort in JP project also, and I am only just plain member in JP project, so I have to debate about it in JP project also, not only here,,, This could speed up the process and improve communications. I am glad to hear from you :) Thank you. -- Taketoshi Sano: [EMAIL PROTECTED]
Re: Homapages in list of maintainers
Hi ! In article [EMAIL PROTECTED] Fumitoshi UKAI [EMAIL PROTECTED] writes: I can volunteer to do it, if it is really needed and anyone object to it. I've been maintain Debian JP machines, ftp archive, web server, mailing-list and Debian official mirror in Japan about two years or three. Thank you for your proposal :). I think it is required very much to get the Debian project to be more global organization as fast as we can, because if more people can join the project smoothly, the project can get more resource to do various task. if someone has the required condition to pass the verification by the New Maintainers Group, I can not find the merit of keep him (or her) in the long waiting queue. If the problem is only related to the human power, the action to do should be to increase the member of the Group, not to keep the queue longer. Adam Di Calro told Remember that approving new maintainer is a very _sensitive_ area, and I think it should be, but if the members in the Debian Project want to make this project to be true global and universal, an action to make the waiting queue shorter should be taken anyway now or in the near future. I am eager to know if anyone has objection. -- Taketoshi Sano: [EMAIL PROTECTED]
Re: Homapages in list of maintainers
also some verification mechanism is required. But I doubt the enoughness and effectiveness of the current processing mechanism. developers-reference told us also: Once this information is received and processed, you should be contacted with information about your new Debian maintainer account. If you don't hear anything within 7-14 days, please send a followup message asking if your original application was received. Do not re-send your original application, that will just confuse the new-maintainer team. Please be patient, especially near release points; mistakes do occasionally happen, and people do sometimes run out of volunteer time. so according to this, I should be waiting at least more 11 days patiently before sending a followup. P.S. I think, and hope that the Debian is open project. -- Taketoshi Sano: [EMAIL PROTECTED]
