craetion of /srv/ftp or /home/ftp by a ftpserver.deb
1) (/srv/) SRV DATA FOR SERVICES PROVIDED BY SYSTEM http://www.debian.org/doc/packaging-manuals/fhs/fhs-2.3.html#SRVDATAFORSERVICESPROVIDEDBYSYSTEM asserts that: no program should rely on a specific subdirectory structure of /srv existing or data necessarily being stored in /srv 2) (/home/) HOME USER HOME DIRECTORIES http://www.debian.org/doc/packaging-manuals/fhs/fhs-2.3.html#HOMEUSERHOMEDIRECTORIES asserts that: no program should rely on this location. Does that mean that an ftpServer.deb is not allowed to issue mkdir /srv/ftp or mkdir /home/ftp ? -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted inadyn 1.96-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 13 Nov 2005 07:10:21 -0600 Source: inadyn Binary: inadyn Architecture: source i386 Version: 1.96-1 Distribution: unstable Urgency: low Maintainer: Shaul Karl [EMAIL PROTECTED] Changed-By: Shaul Karl [EMAIL PROTECTED] Description: inadyn - client to alleviate the requirements for an Internet name Closes: 255606 Changes: inadyn (1.96-1) unstable; urgency=low . * New upstream release. Closes: #255606, src/os_unix.c:71: error: duplicate case value. * debian/changes: Updating it according to the history specifyed in readme.html. * debian/control: Having no-ip.com mentioned in the supported servers. * debian/patches/: + 01_testAndCreateOrigTarBall.dpatch: Also excluding '*/bin/linux/*' and '*/bin/mac/*' from the orig tar ball. + 02_uid_tAndGid_t.dpatch: Updating the line numbers for the patches. + 03_inadyn8ManPage.dpatch: Updated according to upstream changes. * dpatch: Had to build the package where dpatch was not available. Consequently, + The patches were applied manually. + debian/rules: the 2 lines with dpatch were put into comments. + debian/control: /Build-Depends/s/dpatch, // Files: a7acd979eac2f0d41646412cb718807c 567 net optional inadyn_1.96-1.dsc df59f979560807ecb6a7b5bfc0051c04 45403 net optional inadyn_1.96.orig.tar.gz a64c874c5b64ebbc9fd808eec29a82b2 7369 net optional inadyn_1.96-1.diff.gz 7fa6b073b47e9ecd8447f0a9474e9851 23872 net optional inadyn_1.96-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDdtDtqeKiif08kWsRAq43AJsHVpLDUYonuO3EGvWLjrGulnt/agCfXs4S fj09EEY8rhcX5iEeaGyMkeY= =4g1E -END PGP SIGNATURE- Accepted: inadyn_1.96-1.diff.gz to pool/main/i/inadyn/inadyn_1.96-1.diff.gz inadyn_1.96-1.dsc to pool/main/i/inadyn/inadyn_1.96-1.dsc inadyn_1.96-1_i386.deb to pool/main/i/inadyn/inadyn_1.96-1_i386.deb inadyn_1.96.orig.tar.gz to pool/main/i/inadyn/inadyn_1.96.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted inadyn 1.95-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 4 Aug 2005 15:29:16 +0300 Source: inadyn Binary: inadyn Architecture: source i386 Version: 1.95-1 Distribution: unstable Urgency: low Maintainer: Shaul Karl [EMAIL PROTECTED] Changed-By: Shaul Karl [EMAIL PROTECTED] Description: inadyn - client to alleviate the requirements for an Internet name Closes: 255606 Changes: inadyn (1.95-1) unstable; urgency=low . * New upstream release. * debian/changes: Updating it according to the history specifyed in readme.html. * initial uploading to the Debian archive.closes: #255606 (ITP). * debian/rules: + %s/makefile.linux/makefile/ due to upstream making a similar change. + install target: using bin/linux/inadyn rather then bin/inadyn. Once again, this is an upstream modification. * debian/patches/: + 02_setUserGroup.dpatch: Removed as it was merged upstream. + 02_uid_tAndGid_t.dpatch: Added to use Unix uid_t and gid_t. + 03_unixSignals.dpatch: Removed since signals handling were added by upstream. + 03_inadyn8ManPage.dpatch: Document the signals being honored explicitly. * debian/control:Standards-Version: Set to 3.6.2. Files: 5405fc54d011bcb7d96a659bcd0fcf8e 576 net optional inadyn_1.95-1.dsc 44b4f2a41929fbdd6f400126ef2de221 112264 net optional inadyn_1.95.orig.tar.gz 21198c72b52f9c077ba5dc30f4ae6c43 6692 net optional inadyn_1.95-1.diff.gz 327ec5fb456fb1b8a6dd93245c3e2a6e 23386 net optional inadyn_1.95-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDCY+8qeKiif08kWsRAtBQAJ0cMs3kHAxqH420+4bJ7Naxgeu2wwCdGRw4 kmhadcufedAaypBk7nTiEhg= =YVgK -END PGP SIGNATURE- Accepted: inadyn_1.95-1.diff.gz to pool/main/i/inadyn/inadyn_1.95-1.diff.gz inadyn_1.95-1.dsc to pool/main/i/inadyn/inadyn_1.95-1.dsc inadyn_1.95-1_i386.deb to pool/main/i/inadyn/inadyn_1.95-1_i386.deb inadyn_1.95.orig.tar.gz to pool/main/i/inadyn/inadyn_1.95.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: adduser: what is the difference between --disabled-password and--disabled-login
On Mon, May 09, 2005 at 01:14:27PM -0400, Stephen Gran wrote:
This one time, at band camp, Marc Haber said:
On Mon, 09 May 2005 15:34:06 +0300, Shaul Karl [EMAIL PROTECTED] wrote:
adduser(8) states that
With the --disabled-login option, the account will be created but
will be disabled until a password is set. The --disabled-password
option will not set a password, but login are still possible for
example through SSH RSA keys.
I wonder what is the difference?
One disables the account, the other sets an invalid password. I think
that the manpage is quite clear about that.
Perhaps what I really should have asked is about the contents of
/etc/{passwd,shadow}'s password field for disabled accounts.
One is *, the other is !. I never know which is which.
* is disabled, IIRC, and ! is an invalid password (but would still allow
logging in with, e.g, an ssh key). Or so my (often faulty) memory says.
According to shadow(5),
If the password field contains some string that is not valid result of
crypt(3), for instance ! or *, the user will not be able to use a unix
password to log in, subject to pam(7).
The way I understand it, the effect of ! or * is identical.
Alternatively, the difference is set by the configuration of pam, which,
I believe, is out of adduser scope. This match my experience that login
through SSH RSA key is possible even if a '!' is used.
In any case, am I right that adduser's --disabled-login and
--disabled-password looks to be the same?
Why didn't you ask the adduser maintainers?
I need to verify my experience: am I wrong that on a default Debian
system a '!' doesn't prevent login through SSH RSA key? Perhaps a
wishlist bug should be submitted against pam?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
adduser: what is the difference between --disabled-password and--disabled-login
adduser(8) states that
With the --disabled-login option, the account will be created but
will be disabled until a password is set. The --disabled-password
option will not set a password, but login are still possible for
example through SSH RSA keys.
I wonder what is the difference? Alternatively, how adduser accomplish
that? The relevant source lines seem to be:
} elsif ($arg eq quot;--disabled-passwordquot;) {
$ask_passwd = 0;
$disabled_login = 0;
} elsif ($arg eq quot;--disabled-loginquot;) {
$ask_passwd = 0;
$disabled_login = 1;
}
if ($ask_passwd) {
amp;systemcall('/usr/bin/passwd', $new_name);
} else {
if(!$disabled_login) {
amp;systemcall('/usr/sbin/usermod', '-p', '*', $new_name);
}
}
Perhaps what I really should have asked is about the contents of
/etc/{passwd,shadow}'s password field for disabled accounts.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted phpdoc 20030911-1.2 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 6 May 2005 19:44:18 +0300 Source: phpdoc Binary: phpdoc Architecture: source all Version: 20030911-1.2 Distribution: unstable Urgency: low Maintainer: Petr Cech [EMAIL PROTECTED] Changed-By: [EMAIL PROTECTED] Description: phpdoc - Documentation for PHP4 and PHP3 Closes: 282274 Changes: phpdoc (20030911-1.2) unstable; urgency=low . * Non-maintainer upload. * debian/control: - remove openjade from Build-Depends-Indep. (Closes: #282274) - fix standards version to 3.6.1 * debian/README.Debian: fix spelling errors * debian/copyright: remove extra braces (fixes lintian error) Files: 680c0370bca70604318aa0b9a200166d 619 doc optional phpdoc_20030911-1.2.dsc fa672fa22c62429336e1cdc0c4bdce0e 31248 doc optional phpdoc_20030911-1.2.diff.gz 1abf9ceee3ccc378f70f979a573b21f9 1797358 doc optional phpdoc_20030911-1.2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCf5MiqeKiif08kWsRAt+9AJ9B3kNbyW1zpLbj+PGTsuz40f+OOACeP3hB EW5iBDmgKenKPhWh3ODTorM= =xFRh -END PGP SIGNATURE- Accepted: phpdoc_20030911-1.2.diff.gz to pool/main/p/phpdoc/phpdoc_20030911-1.2.diff.gz phpdoc_20030911-1.2.dsc to pool/main/p/phpdoc/phpdoc_20030911-1.2.dsc phpdoc_20030911-1.2_all.deb to pool/main/p/phpdoc/phpdoc_20030911-1.2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gphpedit 0.9.50-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 9 Apr 2005 16:17:45 +0300 Source: gphpedit Binary: gphpedit Architecture: source i386 Version: 0.9.50-2 Distribution: unstable Urgency: low Maintainer: Lior Kaplan [EMAIL PROTECTED] Changed-By: [EMAIL PROTECTED] Description: gphpedit - development environment for PHP/HTML/CSS Closes: 301353 303790 Changes: gphpedit (0.9.50-2) unstable; urgency=low . * debian/control: - Add Shaul Karl [EMAIL PROTECTED] to uploaders. - Fix package description. Closes: #301353 - Add phpdoc to recommends. * Patch tab.c to search the php manual in the right location. Closes: #303790 Files: c430becc2172a20ad22376e1503694b9 646 gnome optional gphpedit_0.9.50-2.dsc 78b2673795490969b984dd7b2d0d84e1 15131 gnome optional gphpedit_0.9.50-2.diff.gz 0d9f57e56c0d3ad2d372bee023974130 367276 gnome optional gphpedit_0.9.50-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCWc3CqeKiif08kWsRAoemAJ0c+EZcH6az+MLv2kj3AmqQqs4LggCeNVrg gBoylWfCdOrop6/u7YAAukQ= =VGUV -END PGP SIGNATURE- Accepted: gphpedit_0.9.50-2.diff.gz to pool/main/g/gphpedit/gphpedit_0.9.50-2.diff.gz gphpedit_0.9.50-2.dsc to pool/main/g/gphpedit/gphpedit_0.9.50-2.dsc gphpedit_0.9.50-2_i386.deb to pool/main/g/gphpedit/gphpedit_0.9.50-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Are there any problems with mirrors.kernel.org/debian?
Am I right that according to mirrors.kernel.org/debian, the archive was not updated for several days? Is that related to the fact that mirrors.kernel.org/debian/ls-lR* have time stamps of 30-Mar-2005? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted tea 7.0-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 16 Feb 2005 23:52:47 +0200 Source: tea Binary: tea Architecture: source i386 Version: 7.0-1 Distribution: unstable Urgency: low Maintainer: Lior Kaplan [EMAIL PROTECTED] Changed-By: [EMAIL PROTECTED] Description: tea- small text editor with syntax highlighting UTF support Closes: 280900 Changes: tea (7.0-1) unstable; urgency=low . * Initial Release. Closes: #280900 * Previous versions where uploaded to http://mentors.debian.net * New upstream release * debian/copyright: update upstream author email address * acknowledge a warning about 'missing' in build time - sent to upstream Files: ebf748c4a7e46a47e59195ef7594fc85 573 editors optional tea_7.0-1.dsc 9c659f2a4caae3b969304bae6f643b78 396692 editors optional tea_7.0.orig.tar.gz 975752ed658417eb9ab45a1edefcf814 10426 editors optional tea_7.0-1.diff.gz 11f1187aea48ed2527716c719f85c4a7 249124 editors optional tea_7.0-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCFpfNqeKiif08kWsRAmsJAJ9VaiRLfJrP36lNe1NqrbaGTlDLAQCfbaIk QszoTsOz7ysg/pOjRBWT0jA= =xBmu -END PGP SIGNATURE- Accepted: tea_7.0-1.diff.gz to pool/main/t/tea/tea_7.0-1.diff.gz tea_7.0-1.dsc to pool/main/t/tea/tea_7.0-1.dsc tea_7.0-1_i386.deb to pool/main/t/tea/tea_7.0-1_i386.deb tea_7.0.orig.tar.gz to pool/main/t/tea/tea_7.0.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gphpedit 0.9.50-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 16 Feb 2005 23:46:58 +0200 Source: gphpedit Binary: gphpedit Architecture: source i386 Version: 0.9.50-1 Distribution: unstable Urgency: low Maintainer: Lior Kaplan [EMAIL PROTECTED] Changed-By: [EMAIL PROTECTED] Description: gphpedit - developemnt environment for PHP/HTML/CSS Closes: 218868 Changes: gphpedit (0.9.50-1) unstable; urgency=low . * Initial Release. (Closes: #218868) * Minor manpage fixes by Ivo [EMAIL PROTECTED] and Andy Jeffries [EMAIL PROTECTED]. Files: fe201702a3586a6e333f9ba5fe2b7cfc 605 gnome optional gphpedit_0.9.50-1.dsc 5683f1f196d8c80bdad587a043423046 829535 gnome optional gphpedit_0.9.50.orig.tar.gz 97fe10a8da4150143be5ef044c77020f 14254 gnome optional gphpedit_0.9.50-1.diff.gz a834b8cba433c4b87a55e544cd87aebb 367090 gnome optional gphpedit_0.9.50-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCFphgqeKiif08kWsRAmlsAJ9VK5BuDnQMiDorelbMFdngD7VX/QCfcNkF hVt5Cj2/iUYGw91p3WRp9/U= =adeD -END PGP SIGNATURE- Accepted: gphpedit_0.9.50-1.diff.gz to pool/main/g/gphpedit/gphpedit_0.9.50-1.diff.gz gphpedit_0.9.50-1.dsc to pool/main/g/gphpedit/gphpedit_0.9.50-1.dsc gphpedit_0.9.50-1_i386.deb to pool/main/g/gphpedit/gphpedit_0.9.50-1_i386.deb gphpedit_0.9.50.orig.tar.gz to pool/main/g/gphpedit/gphpedit_0.9.50.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Switchconf: Orphaning or removing?
I am forwarding this to linux-fai at uni-koeln dot de. I believe many people interested in this discussion hang out there. On Wed, Mar 09, 2005 at 12:35:45PM +0100, Steinar H. Gunderson wrote: On Mon, Mar 07, 2005 at 10:44:25AM +0200, Shaul Karl wrote: 60 PCs with Debian and there exist 4 different configurations? In case each PC has a nic, it sounds like the fai package suits your situation. Or cfengine2 (optionally coupled with pkgsync). /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Switchconf: Orphaning or removing?
On Sun, Mar 06, 2005 at 07:25:46PM +, Jose Manuel dos Santos Calhariz wrote: Yes, I care about it. I use it on my laptop to have personalized configurations for the places I connect to the Internet. For example besides interfaces, I have a sources.list optimized. Now I have to install 60 PCs with Debian and there exist 4 different configurations of monitor, graphical display and mouse. I am using it to switch XF86Config-4 and gpm.conf between the 4 kinds of configurations. There exist any alternative? 60 PCs with Debian and there exist 4 different configurations? In case each PC has a nic, it sounds like the fai package suits your situation. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted efax-gtk 2.2.15-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 27 Feb 2005 01:08:55 +0200 Source: efax-gtk Binary: efax-gtk Architecture: source i386 Version: 2.2.15-1 Distribution: unstable Urgency: low Maintainer: Lior Kaplan [EMAIL PROTECTED] Changed-By: [EMAIL PROTECTED] Description: efax-gtk - front end in Gtk+/Gtkmm for the efax program Changes: efax-gtk (2.2.15-1) unstable; urgency=low . * New upstream release * debian/control: add Shaul Karl (my sponsor) to uploaders, so the package upload wont consider as a NMU. Files: e74710df7bea5a2e3c07b82ddf1aee58 659 comm optional efax-gtk_2.2.15-1.dsc 989c5eef799758a01d90341d24af460f 708848 comm optional efax-gtk_2.2.15.orig.tar.gz e7577aab871acf66f893b83746d8f2ed 28434 comm optional efax-gtk_2.2.15-1.diff.gz ee9b3d6f209e5840b5453c5ac67962e9 634480 comm optional efax-gtk_2.2.15-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCIll3qeKiif08kWsRAnkHAJ9in3fYPh/5wnqzwuAxkxUY5GIq7ACfShtT UCgPdRdj/PRV0pmMCVCjlVE= =/1FW -END PGP SIGNATURE- Accepted: efax-gtk_2.2.15-1.diff.gz to pool/main/e/efax-gtk/efax-gtk_2.2.15-1.diff.gz efax-gtk_2.2.15-1.dsc to pool/main/e/efax-gtk/efax-gtk_2.2.15-1.dsc efax-gtk_2.2.15-1_i386.deb to pool/main/e/efax-gtk/efax-gtk_2.2.15-1_i386.deb efax-gtk_2.2.15.orig.tar.gz to pool/main/e/efax-gtk/efax-gtk_2.2.15.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted efax-gtk 2.2.14-3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 21 Feb 2005 00:01:12 +0200 Source: efax-gtk Binary: efax-gtk Architecture: source i386 Version: 2.2.14-3 Distribution: unstable Urgency: low Maintainer: Lior Kaplan [EMAIL PROTECTED] Changed-By: [EMAIL PROTECTED] Description: efax-gtk - front end in Gtk+/Gtkmm for the efax program Closes: 296058 Changes: efax-gtk (2.2.14-3) unstable; urgency=low . * Fix package short description (Closes: #296058). Files: 440647355d9e56703542f5bf3c9e4225 618 comm optional efax-gtk_2.2.14-3.dsc 769fb0fa969ab0c4e60070bd8c1fc7c9 28343 comm optional efax-gtk_2.2.14-3.diff.gz 47e33862c24e814da59e250e40d48575 613684 comm optional efax-gtk_2.2.14-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCGkgUqeKiif08kWsRAiDlAJ91YkrUwJfNApmL1N5yDw+lzGmSoQCdFCnm 1kI+HrUGXPug3m0m1EP1lQU= =0wR+ -END PGP SIGNATURE- Accepted: efax-gtk_2.2.14-3.diff.gz to pool/main/e/efax-gtk/efax-gtk_2.2.14-3.diff.gz efax-gtk_2.2.14-3.dsc to pool/main/e/efax-gtk/efax-gtk_2.2.14-3.dsc efax-gtk_2.2.14-3_i386.deb to pool/main/e/efax-gtk/efax-gtk_2.2.14-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted efax-gtk 2.2.14-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 5 Jan 2005 23:40:30 +0200 Source: efax-gtk Binary: efax-gtk Architecture: source i386 Version: 2.2.14-1 Distribution: unstable Urgency: low Maintainer: Lior Kaplan [EMAIL PROTECTED] Changed-By: [EMAIL PROTECTED] Description: efax-gtk - font end in Gtk+/Gtkmm for the efax program Closes: 270075 283931 Changes: efax-gtk (2.2.14-1) unstable; urgency=low . * New maintainer (Closes: #283931). * New upstream release (Closes #262149). * In version 2.2.0b, Handling different codeset chars in .efax-gtkrc was fixed (Closes #222736). * Upstream fixed build problem with gcc 3.4 (Closes: #270075). * debian/control:Build-Depends: Ommiting libpango1.0-dev and libatk1.0-dev as some of the other Build-Depends will pull them in. * Checked the compilation warnings with upstream. Nothing to do right now. Files: e9c01122a0d6a24384727c67fcc9ecb1 618 comm optional efax-gtk_2.2.14-1.dsc e0f1bac3edfbb9fedee214e9fd74b94c 667686 comm optional efax-gtk_2.2.14.orig.tar.gz 5400a8d1d62598ec68c2248c034505ac 28275 comm optional efax-gtk_2.2.14-1.diff.gz 484c593feb702a35b6b42d24087a09b6 614016 comm optional efax-gtk_2.2.14-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFB7A6jqeKiif08kWsRAjr3AJ4piozA2s6vS5LJjRzLAYlCWGF0UgCfTImO ZTQBlxqgDE2/sgWFuqMtNWA= =pgG9 -END PGP SIGNATURE- Accepted: efax-gtk_2.2.14-1.diff.gz to pool/main/e/efax-gtk/efax-gtk_2.2.14-1.diff.gz efax-gtk_2.2.14-1.dsc to pool/main/e/efax-gtk/efax-gtk_2.2.14-1.dsc efax-gtk_2.2.14-1_i386.deb to pool/main/e/efax-gtk/efax-gtk_2.2.14-1_i386.deb efax-gtk_2.2.14.orig.tar.gz to pool/main/e/efax-gtk/efax-gtk_2.2.14.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted tkman 2.2-1 (all source)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 29 Apr 2004 00:28:53 +0300
Source: tkman
Binary: tkman
Architecture: source all
Version: 2.2-1
Distribution: unstable
Urgency: low
Maintainer: Shaul Karl [EMAIL PROTECTED]
Changed-By: Shaul Karl [EMAIL PROTECTED]
Description:
tkman - A graphical, hypertext manual page and Texinfo browser
Closes: 235844
Changes:
tkman (2.2-1) unstable; urgency=low
.
* New upstream release: reviewed for Tcl/Tk 8.4. Closes: #235844.
* Makefile: setting wish to /usr/bin/wish. The package will now be
using Debian's alternatives machanism.
* debian/doc{s,-base}: s/tkman-help/manual/
* debian/copyright: s/author(s)/author/.
* debian/{copyright,watch}: updated the URL from where the source
was downloaded.
* debian/rules: Modified to use dpacth with patch and unpatch targets.
* debian/control:
+ s/Build-Depends/Build-Depends-Indep/.
+ Building also depends now on dpatch and patch.
+ Now conforming with Standards-Version 3.6.1.0.
+ Versions of packages mentioned in the file were updated.
+ Removed the suggestion for printing daemons and utilities.
* Adding some comments to Debian's specific patches.
Files:
ae8d06b35293e8a8cb3b8389bad80bde 567 doc optional tkman_2.2-1.dsc
0e81735c93ab2500d6105ff33095c3e8 229273 doc optional tkman_2.2.orig.tar.gz
e188ad5c96bae9e32a9a9e01a850f13d 9895 doc optional tkman_2.2-1.diff.gz
e4da6decdec4d8a631bf110f63ab4b58 196206 doc optional tkman_2.2-1_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAlV2tqeKiif08kWsRAk3VAJ9oID63dCgbHyhITAXkMBYpVA1a6gCeOHU+
17yv0fJOwfiOvKwxNThEQiU=
=6iau
-END PGP SIGNATURE-
Accepted:
tkman_2.2-1.diff.gz
to pool/main/t/tkman/tkman_2.2-1.diff.gz
tkman_2.2-1.dsc
to pool/main/t/tkman/tkman_2.2-1.dsc
tkman_2.2-1_all.deb
to pool/main/t/tkman/tkman_2.2-1_all.deb
tkman_2.2.orig.tar.gz
to pool/main/t/tkman/tkman_2.2.orig.tar.gz
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
pbuilder and sid.
How can I create a base.tgz which will be useable for pbuilder with sid? 1. pbuilder update --distribution sid --logfile /var/cache/pbuilder/sid/log/update --override-config --basetgz /var/cache/pbuilder/sid/base.tgz where /var/cache/pbuilder/sid/base.tgz is the one I use for sarge gives repeated messages of W: Retrying to unmount proc umount: /var/cache/pbuilder/build/24115/proc: device is busy Could not unmount proc, there might be some program still using files in /proc (klogd?). Please check and kill it so that I can unmount proc and indeed mount shows that /proc on /var/cache/pbuilder/build/24115/proc type proc (rw) /dev/pts on /var/cache/pbuilder/build/24115/dev/pts type devpts (rw) 2. pbuilder create also failed. pbuilder create --distribution sid --logfile /var/cache/pbuilder/sid/log/create ended with I: Installing core packages... dpkg: `update-rc.d' not found on PATH. dpkg: 1 expected program(s) not found on PATH. NB: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin. W: Failure trying to run: chroot /var/cache/pbuilder/build/21503/. dpkg --force-depends --install /var/cache/apt/archives/base-files_3.0.8_i386.deb /var/cache/apt/archives/base-passwd_3.5.3_i386.deb pbuilder: debootstrap failed - Aborting with an error - cleaning the build env -- Shaul Karl, [EMAIL PROTECTED] e t
Re: O: libsafe -- Protection against buffer overflow vulnerabilities
Although I do not want to adopt it I have prepared an NMU based on Yotam's work. The changelog is: libsafe (2.0-9-1) unstable; urgency=low * New upstream release. Closes: Bug#118786 * Removed dependency on ldso. Closes: Bug#117339 * libsafe no longer maintains its own implementation of libc routines. Closes: Bug#122640, Bug#122706, Bug#77949, Bug#104116 * libsafe should now work properly with glibc: example exploits no longer work. Closes: Bug#92336 * Added libsafe wrapper. Closes: Bug#126421 * Example exploits are no longer executable by default. * All the above was done by Yotam Rubin [EMAIL PROTECTED] who is waiting for DAM approval. * s/\(DESTDIR[[:space:]]*= \)/\1`pwd`\/..\/debian\/tmp\// src/makefile. * s/\($(DESTDIR)\/usr\)/\1\/share/ src/makefile. * Added a Build-Depends: debhelper line. * Non-maintainer upload due to the long time this package has not been uploaded and the maintainer just orphaning it. -- Shaul Karl [EMAIL PROTECTED] Mon, 31 Dec 2001 00:42:21 +0200 Should I upload it? Package: wnpp Severity: normal The current maintainer of libsafe, Ron Rademaker [EMAIL PROTECTED], has orphaned this package. If you want to be the new maintainer, please take it -- retitle this bug from 'O:' to 'ITA:', fix the outstanding bugs and upload a new version with your name in the Maintainer: field and a * New maintainer (Closes: #thisbug) in the changelog so this bug is closed. Some information about this package: Package: libsafe Priority: optional Section: libs Installed-Size: 256 Maintainer: Ron Rademaker [EMAIL PROTECTED] Architecture: i386 Version: 1.3-6 Depends: libc6 (= 2.1.2), ldso (= 1.8.5) Suggests: ldso (= 1.9.0), ld.so.preload-manager (= 0.1) Filename: pool/main/libs/libsafe/libsafe_1.3-6_i386.deb Size: 147848 MD5sum: 5902ee9bca4d0d22b637a06f940e0ecc Description: Protection against buffer overflow vulnerabilities Libsafe is a library that works with any pre-compiled executable and can be used transparently. Libsafe intercepts calls to functions known as vulnerable, libsafe uses a substitute version of the function that implements the same functionality, but makes sure any buffer overflows are contained within the current stack frame. * Ron Rademaker [EMAIL PROTECTED] [20011227 14:17]: You're right that I haven't done anything about libsafe where I should have... I guess the best thing to do right now is put libsafe up for adoption. On Thu, 27 Dec 2001, Matthias Klose wrote: Yotam Rubin writes: Greetings, The last libsafe upload has been over a year ago. Since then, libsafe has accumulated a large number of bugs. The current Debian release doesn't seem to be very effective. I've packaged the latest libsafe and made it available at: http://192.117.130.34/Fendor/debian/libsafe/ Can someone NMU that? I've contacted the maintainer but received no reply. It's a shame that libsafe wouldn't be usable for Debian users. - the upload isn't marked as a NMU - the package does not build from source (calls ldconfig): - the package does not build a -dev package. Correct? - the package overwrites the old library? Correct, if it's an extension only. But then it needs to be marked in the shlibs file. Else you need to build a libsafe2 and libsafe-dev package. OTOH, no package depends on libsafe. So it seems, we don't gain much to replace one buggy version with the next buggy version. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Martin Michlmayr [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Shaul Karl email: shaulka(at-no-spam)bezeqint.net Please replace (at-no-spam) with an at - @ - character. (at-no-spam) is meant for unsolicitate mail senders only.
Re: iso 8859-6 fonts
On Fri, Sep 21, 2001 at 05:21:39AM +0300, Shaul Karl wrote: [05:09:10 tmp]$ grep-available -PX xfonts-intl-arabic Package: xfonts-intl-arabic Which are couple of fonts in an Emacs-only encoding, not useful outside of Emacs. Please note that in general Linux distros have problems with Arabic that are much severe then the fonts issue: The right to left (RTL) direction and the changing of the font according to context (or something similar) are way from being solved, especially, but not limited to, text consoles. And these are far difficult problems then one might think at first look. For a large set of programs, the solution is using QT 3.0 or libgtk 2.4 (or is it 3.0?). I still do not find it satisfactory, mostly because it is not part of the native Unix environment and as such not suited for console apps. Hopefully you will find interest in the [EMAIL PROTECTED] mailing list. Although it is administrated by an Israeli volunteers, it does have participants from other countries. And this is because the RTL problem is shared among Arabic and Hebrew. But RTL is only a part of the problem. Arabeyes is a much better site for general Arabization, including Arabic font making. -- David Starner - [EMAIL PROTECTED] Pointless website: http://dvdeug.dhis.org When the aliens come, when the deathrays hum, when the bombers bomb, we'll still be freakin' friends. - Freakin' Friends -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Shaul Karl [EMAIL PROTECTED]
Re: iso 8859-6 fonts
yeah RTL is true about arabic . And it could be solved by making an arabic keymap . That is the point. As far as I know, The it is far more complex then one tend to think at first glance, especially when you want multi lingual support. And the keymap, which can be made quite easily is only an input method. It does not concern the heart of the problem. Just for curiosity , do you have arabic developers who maintain arabic fonts/programs ? http://www.debian.org/devel/developers.loc does not show many. Still, it could be that no one of them has entered his geographical data and thus does not get to be on the map. It could also be that some of them are living in other parts of the world. Yet I do tend to believe that there are very few Arab developers. I also believe that there is a great need for developers who will concentrate on Arabic and, perhaps more importantly, on embedding Arabic, RTL and multi lingual in the Unix environment. In any case you can search by specific countries in http://db.debian.org If yes , may i know who ? if no , can some one apply to do so ? You might want to read http://nm.debian.org in order to see how to apply to be a developer and what you will need in order to become one. However in case you are new to Unix you might want to wait until you will have more experience. Thanks all for your help -- On Fri, 21 Sep 2001 02:16:42 David Starner wrote: On Fri, Sep 21, 2001 at 05:21:39AM +0300, Shaul Karl wrote: [05:09:10 tmp]$ grep-available -PX xfonts-intl-arabic Package: xfonts-intl-arabic Which are couple of fonts in an Emacs-only encoding, not useful outside of Emacs. Please note that in general Linux distros have problems with Arabic that are much severe then the fonts issue: The right to left (RTL) direction and the changing of the font according to context (or something similar) are way from being solved, especially, but not limited to, text consoles. And these are far difficult problems then one might think at first look. For a large set of programs, the solution is using QT 3.0 or libgtk 2.4 (or is it 3.0?). Hopefully you will find interest in the [EMAIL PROTECTED] mailing list. Although it is administrated by an Israeli volunteers, it does have participants from other countries. And this is because the RTL problem is shared among Arabic and Hebrew. But RTL is only a part of the problem. Arabeyes is a much better site for general Arabization, including Arabic font making. -- David Starner - [EMAIL PROTECTED] Pointless website: http://dvdeug.dhis.org When the aliens come, when the deathrays hum, when the bombers bomb, we'll still be freakin' friends. - Freakin' Friends Join 18 million Eudora users by signing up for a free Eudora Web-Mail account at http://www.eudoramail.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Shaul Karl [EMAIL PROTECTED]
Re: iso 8859-6 fonts
On Sun, Sep 23, 2001 at 10:16:02PM +0300, Shaul Karl wrote: For a large set of programs, the solution is using QT 3.0 or libgtk 2.4 (or is it 3.0?). I still do not find it satisfactory, mostly because it is not part of the native Unix environment and as such not suited for console apps. The Linux console may never get proper RTL support; decent Arabic support on the console would be hard to impossible given console font limitations. Complex scripts are going to need X support; at the very least, you're going to need to run in an Xterm or the like, since Linux console is probably always going to be LTR, single width, and non-combining. There has to be a standard way to at least have basic unix utils like grep, ed, diff and friends to work on files with multi lingual contents and still have a reasonable user interface and means to display their output. -- David Starner - [EMAIL PROTECTED] Pointless website: http://dvdeug.dhis.org When the aliens come, when the deathrays hum, when the bombers bomb, we'll still be freakin' friends. - Freakin' Friends -- Shaul Karl [EMAIL PROTECTED]
Re: iso 8859-6 fonts
Hi there I dont find any packge that supports iso 8859-6 -- that is arabic fonts . [05:09:10 tmp]$ grep-available -PX xfonts-intl-arabic Package: xfonts-intl-arabic Priority: optional Section: x11 Installed-Size: 62 Maintainer: Milan Zamazal [EMAIL PROTECTED] Architecture: all Source: intlfonts Version: 1.2-2 Replaces: intlfonts-arabic Depends: xutils (= 4.0.2) Suggests: xfs | xserver Conflicts: intlfonts-arabic Filename: pool/main/i/intlfonts/xfonts-intl-arabic_1.2-2_all.deb Size: 17322 MD5sum: c0142cdaa2f4485c1070e9a5d064407f Description: International fonts for X -- Arabic. This package includes some Arabic fonts (digits and single and double column). [05:09:39 tmp]$ Do you need some arabic people to participate in arabic fonts project ? It would be my pleasure . Im from Kuwait and arabic is my mother tongue . Please note that in general Linux distros have problems with Arabic that are much severe then the fonts issue: The right to left (RTL) direction and the changing of the font according to context (or something similar) are way from being solved, especially, but not limited to, text consoles. And these are far difficult problems then one might think at first look. Hopefully you will find interest in the [EMAIL PROTECTED] mailing list. Although it is administrated by an Israeli volunteers, it does have participants from other countries. And this is because the RTL problem is shared among Arabic and Hebrew. Thanks Join 18 million Eudora users by signing up for a free Eudora Web-Mail account at http://www.eudoramail.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Shaul Karl [EMAIL PROTECTED]
Re: How to make your custom debian packages apt-gettable
I wrote a documentation How to make your custom debian packages apt-gettable. Have I re-invented the wheel? sgml (DocBook) source http://www.interq.or.jp/libra/oohara/apt-gettable/apt-gettable.sgml html version (formatted with NewbieDoc style sheet) http://www.interq.or.jp/libra/oohara/apt-gettable/apt-gettable/index.html html in tarball http://www.interq.or.jp/libra/oohara/apt-gettable/apt-gettable.tar.gz Perhaps we should have a www.debian.org/doc/ddp/suggested where many preliminaries, drafts, hardly maintained and similar Debian specific (mini) HOWTOs will be put? It could be a better place for this packages apt-gettable HOWTO and hopefully many other docs that are spread all over the net. -- Oohara Yuuma [EMAIL PROTECTED] Graduate-school of Science, Kyoto University PGP Key http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star a way -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Shaul Karl [EMAIL PROTECTED] -- Shaul Karl [EMAIL PROTECTED]
Re: Two debconf issues
On Thu, May 03, 2001 at 05:00:29PM -0400, Joey Hess wrote: Wolfgang Sourdeau wrote: It might happen if there was a good reason, but nobody has suggested one yet. I doubt there is one. I have one. It's that dependency on perl makes owners of 486 machines die of an heart-attack whenever an installation task has to occur... Bollocks. Profile running perl sometime. Then profile running dpkg. Let me second this. Perl is very, very fast. Perl is faster than most people's hand-crafted C code for certain tasks (mainly pattern matching type tasks, also its associative array implementation is pretty nippy). On my 68020 machine, using a short perl script was an order of magnitude faster than sed or awk, even for exactly the kind of pattern matching tasks that sed and awk are designed for. Perl ain't your problem, it really ain't. Jules Can you compare Perl speed to Python? Just curious, have no prior knowledge on this. -- Shaul Karl [EMAIL PROTECTED]
Re: Bug#95430 acknowledged by developer (Re: Bug#95430: ash: word-splitting changes break shell scripts)
Herbert Xu [EMAIL PROTECTED] writes:
Not only does that show that Solaris 2.6's shell does not set IFS,
windlord:~ printenv IFS
windlord:~ /bin/sh -c 'echo x-${IFS}-x'
x- -x
windlord:~ uname -a
SunOS windlord.stanford.edu 5.6 Generic_105181-19 sun4u sparc SUNW,Ultra-1
Looks set to me, although it appears to be set incorrectly.
Incorrectly? Looks to me the same as with bash:
[16:24:40 tmp]$ printenv IFS
[16:24:46 tmp]$ bash -c 'echo x-${IFS}-x'
x- -x
[16:24:48 tmp]$ bash --version
GNU bash, version 2.05.0(1)-release (i386-pc-linux-gnu)
Copyright 2000 Free Software Foundation, Inc.
[16:27:28 tmp]$
Ah, something might be wrong with the above tests:
[16:35:41 tmp]$ set | grep IFS
IFS=$' \t\n'
[16:35:59 tmp]$
Solaris's /bin/sh isn't a particularly good example, as it's one of the
most completely broken Bourne shells shipped with a modern OS. It doesn't
even try to be POSIX-compliant.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
--
Shaul Karl [EMAIL PROTECTED]
Re: Only one who have parse error in /var/lib/dpkg/available?
On Wed, 25 Apr 2001, Shaul Karl wrote: Package: ng-cjk Priority: optional Section: editors Installed-Size: 164 Maintainer: Yasuhiro Take [EMAIL PROTECTED] Architecture: i386 Source: ng Version: 1.4.3.1-1 Depends: libc6 (= 2.2.1), libncurses5, ng-common Filename: pool/main/n/ng/ng-cjk_1.4.3.1-1_i386.deb Size: 73550 MD5sum: dcf8a20ce9180fa42df [22:46:18 /tmp]$ wc /var/lib/dpkg/available 69953 307766 2547713 /var/lib/dpkg/available [22:46:41 /tmp]$ Is there a final new line? Yes there is: [12:36:41 /tmp]$ ls -l /var/lib/dpkg/available -rw-r--r--1 root root 2547713 Apr 25 00:46 /var/lib/dpkg/available [12:39:36 /tmp]$ od -cj 2547700 /var/lib/dpkg/available 11557764 c e 9 1 8 0 f a 4 2 d f \n 11560001 [12:39:42 /tmp]$ and dpkg -l doc-linux-text works too. I do not know what was changed. Shouldn't there be a Description field after the MD5sum? -- Shaul Karl [EMAIL PROTECTED]
Re: Only one who have parse error in /var/lib/dpkg/available?
On Thu, 26 Apr 2001, Shaul Karl wrote: Yes there is: [12:36:41 /tmp]$ ls -l /var/lib/dpkg/available -rw-r--r--1 root root 2547713 Apr 25 00:46 /var/lib/dpkg/available [12:39:36 /tmp]$ od -cj 2547700 /var/lib/dpkg/available 11557764 c e 9 1 8 0 f a 4 2 d f \n 11560001 [12:39:42 /tmp]$ and dpkg -l doc-linux-text works too. I do not know what was changed. No, there is no final new line. debian-devel1:/# od -cj 5199880 /var/lib/dpkg/available 23654010 r d . \n \n It looks like the file got truncated. Disk corruption? What apt-cache dumpavail(called from dselect [2]) interrupted? I am not sure but the reason could also be a problem with a local server. At least for now, after an apt-get update from another server, it looks O.K: 1) The size of the file has grown a lot. 2) Now there is the terminating \n\n. [22:49:47 /tmp]$ od -cj 4462910 /var/lib/dpkg/available 21014476 f o r m s . \n \n 21014507 [22:52:04 /tmp]$ 3) The Description is the last field. I will watch it. Thank you for the help. -- Shaul Karl [EMAIL PROTECTED]
Re: Only one who have parse error in /var/lib/dpkg/available?
--pgp-sign-Multipart_Fri_Apr_27_01:25:02_2001-1
Content-Type: text/plain; charset=US-ASCII
At Thu, 26 Apr 2001 00:14:01 -0500 (CDT),
[EMAIL PROTECTED] wrote:
On Thu, 26 Apr 2001, Shaul Karl wrote:
Yes there is:
[12:36:41 /tmp]$ ls -l /var/lib/dpkg/available
-rw-r--r--1 root root 2547713 Apr 25 00:46
/var/lib/dpkg/available
[12:39:36 /tmp]$ od -cj 2547700 /var/lib/dpkg/available
11557764 c e 9 1 8 0 f a 4 2 d f \n
11560001
[12:39:42 /tmp]$
and
dpkg -l doc-linux-text
works too. I do not know what was changed.
No, there is no final new line.
debian-devel1:/# od -cj 5199880 /var/lib/dpkg/available
23654010 r d . \n \n
It looks like the file got truncated. Disk corruption? What apt-cache
dumpavail(called from dselect [2]) interrupted?
I guess it is my fault. Maybe the description of ng-cjk lacks final new-line
like below, and i guess that's the cause.
I am quite sure it is not your fault.
Although I do not know the cause I run an
apt-get update
for testing from another server. Now everything seems to be fine. There is
here a problem with the local server and I hope that this, and not my machine,
are the cause. In addition, no one else has reported to have the same problem.
[01:24:48 /tmp]$ grep -A20 '^Package: ng-cjk$' /var/lib/dpkg/available
Package: ng-cjk
Priority: optional
Section: editors
Installed-Size: 164
Maintainer: Yasuhiro Take [EMAIL PROTECTED]
Architecture: i386
Source: ng
Version: 1.4.3.1-1
Depends: libc6 (= 2.2.1), libncurses5, ng-common
Filename: pool/main/n/ng/ng-cjk_1.4.3.1-1_i386.deb
Size: 73550
MD5sum: dcf8a20ce9180fa42df4bd7dc512d6f8
Description: Nihongo MicroGnuEmacs with CJK support.
Ng is Nihongo Mg, MicroGnuEmacs. It is a small lightweight Emacs-like
editor. It can handle both Latin and CJK.
.
ng-cjk can handle ISO-2022-JP, Shift-JIS, EUC-JP as well as EUC-KR and
EUC-CN(GB only). Latin is not supported.
Package: ng-cjk-canna
Priority: optional
[01:24:51 /tmp]$
sed 's/^ /+/' control | grep -A 11 '^Package: ng-cjk$'
Package: ng-cjk
Architecture: any
Depends: ${shlibs:Depends}, ng-common
Description: Nihongo MicroGnuEmacs with CJK support.
+Ng is Nihongo Mg, MicroGnuEmacs. It is a small lightweight Emacs-like
+editor. It can handle both Latin and CJK.
+.
+ng-cjk can handle ISO-2022-JP, Shift-JIS, EUC-JP as well as EUC-KR and
+EUC-CN(GB only). Latin is not supported.
+
Package: ng-cjk-canna
Architecture: any
I'll fix this right now and dupload it.
Thanks,
hirot
--pgp-sign-Multipart_Fri_Apr_27_01:25:02_2001-1
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQA66EvhfGUzr9MtPXERAoN0AKDKOojJg/Ooun07mLXhJc+6qE50sgCgrHZZ
NoU5vW2XMI+BDAW+w62aHxE=
=ru2q
-END PGP SIGNATURE-
--pgp-sign-Multipart_Fri_Apr_27_01:25:02_2001-1--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
--
Shaul Karl [EMAIL PROTECTED]
Re: Only one who have parse error in /var/lib/dpkg/available?
Previously Shaul Karl wrote: [00:44:26 /tmp]$ dpkg -l doc-linux-text dpkg: parse error, in file `/var/lib/dpkg/available' near line 69953 package `ng-cjk': EOF during value of field `MD5sum' (missing final newline) Show is that line and the few lines around it please. Wichert. -- / Generally uninteresting signature - ignore at your convenience \ | [EMAIL PROTECTED] http://www.liacs.nl/~wichert/ | | 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D | [22:46:04 /tmp]$ grep -A15 -B3 ng-cjk /var/lib/dpkg/available some awkwardnesses in the semantics (for instance, moving a file to a different directory will render its file handle invalid). Package: ng-cjk Priority: optional Section: editors Installed-Size: 164 Maintainer: Yasuhiro Take [EMAIL PROTECTED] Architecture: i386 Source: ng Version: 1.4.3.1-1 Depends: libc6 (= 2.2.1), libncurses5, ng-common Filename: pool/main/n/ng/ng-cjk_1.4.3.1-1_i386.deb Size: 73550 MD5sum: dcf8a20ce9180fa42df [22:46:18 /tmp]$ wc /var/lib/dpkg/available 69953 307766 2547713 /var/lib/dpkg/available [22:46:41 /tmp]$ It looks like the MD5sum is the last line on this file. Another thing is that dpkg -l doc-linux-text now doesn't care - do not know why. Could be that I have added a '\n' there by hand, but I am not sure. -- Shaul Karl [EMAIL PROTECTED]
Only one who have parse error in /var/lib/dpkg/available?
[00:44:26 /tmp]$ dpkg -l doc-linux-text dpkg: parse error, in file `/var/lib/dpkg/available' near line 69953 package `ng-cjk': EOF during value of field `MD5sum' (missing final newline) [00:44:45 /tmp]$ Am I the only one who has it? I have a apt-cache dumpavail /var/lib/dpkg/available; line in my /etc/apt/apt.conf DPkg section if this makes any difference. -- Shaul Karl [EMAIL PROTECTED]
Re: please help updating calendar
On Sep 08, Julian Gilbey [EMAIL PROTECTED] wrote: Their list is much more comprehensive than mine, but mine contains far more detail. So it's worth merging them, but I'm not quite sure how you'd like to do this. There is also the implicit assumption in their If there are no fixed events then everything should go in the yearly files. The events are fixed. The main point is that the Jewish calendar is based on the motion of the moon, so that a regular Jewish year is 354 days long (Yet there are years with an extra month and maybe other mechanisms to compensate for that). But as far as I know every Jewish event could be calculated in advance. calendar that the user is Orthodox and living outside of Israel, neither of which need be true. Maybe we should have more than one calendar? I believe that merging the files is better. As far as I know most of the dates are the same, regardless of whether you live in Israel or outside it. And in any case people who live in Israel would likely be interested to know what are the dates for people who live outside of Israel and vice versa. -- ciao, Marco -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- -- Shaul Karl [EMAIL PROTECTED] Donate free food to the world's hungry: see http://www.thehungersite.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Becoming a Pkg Mgr.
On Thu, Mar 23, 2000 at 10:32:06AM -0800, Jason C. Leach wrote: hi, How does one become a package manager? I could probably spair enough time to look after one. The New Maintainer team will be re-opening shortly. In the meantime, keep an eye on debian-devel-announce, start reading lists, look for something useful to do, maybe help to correct some bugs, and possibly take part in the sponsoring system (can't remember the URL to look at offhand; check out the -devel-announce archives for the last several months -- maybe it was last summer?). http://www.internatif.org/bortzmeyer/debian/sponsor/ Read the policy and packaging manuals, the developer's reference and of course the Debian Social Contract and DFSG. Good luck! Julian -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Julian Gilbey, Dept of Maths, QMW, Univ. of London. [EMAIL PROTECTED] Debian GNU/Linux Developer, see http://www.debian.org/~jdg Donate free food to the world's hungry: see http://www.thehungersite.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Shaul Karl [EMAIL PROTECTED] An elephant is a mouse with an operating system.
Re: An advise how to apply for the TkMan author to change his license.
On Wed, Mar 08, 2000 at 03:18:47AM +0200, Shaul Karl wrote: [22:42:00 src]$ tail -n 9 tkman-2.1b4/README-tkman Permission to use, copy, modify, and distribute this software and its documentation for documentation for any purpose, without fee, and without a written agreement is hereby granted. This software is provided on as as is basis, without any warranty whatsoever. documentation for documentation for looks like a classic typo (where the typist loses track of what's been typed and types a phrase twice). If that's the case it should be a trivial fix. The situation is that I am trying to maintain TkMan while applying to be a debian maintainer. The new TkMan license is stated above. Yet as far as I understand this license is not enough for asking to get TkMan into main since TkMan depends on rman which is in non-free. It's been more then a week when I posted my message but Stephen M. Moraco [EMAIL PROTECTED], the debian maintainer of rman did not reply me. Should I wait more? Should I email him my message again? Is that because I am not a debian maintainer? I am considering approaching the author again, this time about rman. I already approached him about TkMan and he seems to be most cooperative. Suppose I was a debian maintainer, is it ethical of me to approach the upstream author about a package that I do not maintain claiming that one of my motivations is the desire to put TkMan into debian's main pool? Are there any other reasons why I should not approach him? -- Shaul Karl [EMAIL PROTECTED] An elephant is a mouse with an operating system.
Re: official brand for cdroms
maybe the term offical for cdroms be used, if someone sells a set of cdroms, constisting of the official cdroms and an extra cd with things like debian-non-US, debian-non-free (those parts that are allowed to be burned and sold), and other stuff like 2.0 + 2.1 kernel source, netscape, mozilla, kde ... ? does anyone know how dselect can handle installing packages from several cd's ? 1) I also think that such CDs are desirable. Is there somewhere such a collection ? 2) direct invokation of dpkg could always be used to overcome dselect limitations (or my lack of knowledage on how to use dselect). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
