No space left on device on haydn
To administrators of haydn in special and others just for the record. Kind regards Andreas. -- Forwarded message -- Date: Wed, 30 Mar 2005 07:58:43 + From: Mail Delivery System <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Mail delivery failed: returning message to sender This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: pipe to |/var/lib/mailman/mail/wrapper post pkg-zope-developers generated by [EMAIL PROTECTED] local delivery failed The following text was generated during the delivery attempt: -- pipe to |/var/lib/mailman/mail/wrapper post pkg-zope-developers generated by [EMAIL PROTECTED] -- Traceback (most recent call last): File "/var/lib/mailman/scripts/post", line 94, in ? main() File "/var/lib/mailman/scripts/post", line 89, in main msg.Enqueue(mlist, tolist=1) File "/usr/lib/mailman/Mailman/Message.py", line 178, in Enqueue dbfp.close() IOError: [Errno 28] No space left on device -- This is a copy of the message, including all the headers. -- ... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#302138: incorrect Description line wrapping with bullet lists
Package: linda
Version: 0.3.10
Severity: wishlist
ObListCC: search for 'mass bug' below.
Lots of packages have a Description field that includes a bullet list.
There is no good way to do these, unfortunately, but lots of wrong
ways. In particular, you'll cause incorrect line wrapping in dselect
or aptitude if you don't indent each bullet by at least one space.
Take for example db4.1-util 4.1.25-18:
| This package provides different tools for manipulating databases
| in the Berkeley v4.1 database format, and includes:
| - db4.1_archive: write the pathnames of the log files no longer in use.
| - db4.1_checkpoint: daemon process to monitor the database log and checkpoint
| it periodically.
| - db4.1_deadlock: traverse the database environment lock region and abort
| lock requests when a deadlock is detected.
The first 4 lines will wrap freely, which is wrong, and the "it
periodically" won't wrap back to the previous line, which is also
wrong.
The best way to do bullet points is to indent the line with the bullet
character on it. Another way is to separate bullet points with " ."
lines, instead of indenting them. Either way you must _not_ indent any
followup lines. Neither form renders ideally well, but at least they
word-wrap correctly.
I'd like to file a mass bug for these, but it's on the order of 583
binary packages in 430 source packages, so I obviously want to get some
feedback first.
Common bullet characters are "-", "*" and "o". Linda could flag a
warning if a description includes the regex "^ [-*o] " which does not
immediately follow "^ \.$". That's one problem case. The other would
be a line "^ *[-*o] " followed immediately by "^ " but not another
"^ *[-*o] ". Please find attached a quick perl script I cooked up for
piping a Packages file into, as proof of concept.
#!/usr/bin/perl -nl
BEGIN {
print "# issue_1: line starting with bullet wraps to previous line";
print "# issue_2: line following bullet doesn't wrap with it";
print "#";
print "# SRC_PKG BIN_PKG - problem";
sub whine {
my ($n) = @_;
if (!$inf[$n]->{$p}++) {
print "$s $p - issue_$n"
}
}
}
chomp;
if (m/^Package: (.*)/) { $s = $p = $1 }
if (m/^Source: (.*)/) { $s = $1 }
if (!$dot and m/^ [-*o] /) { whine(1) }
if ($bul and m/^ / and !m/^ *[-*o] /) { whine(2) }
if ($_ eq ' .') { $dot = 1 } else { $dot = 0 }
if (m/^ *[-*o] /) { $bul = 1 } else { $bul = 0 }
signature.asc
Description: Digital signature
Re: Bug#302138: incorrect Description line wrapping with bullet lists
[Peter Samuelson] > I'd like to file a mass bug for these, but it's on the order of 583 > binary packages in 430 source packages, so I obviously want to get > some feedback first. Jeroen van Wolffelaar pointed out to me that 430 source packages is a bit much for a mass bug, especially if lintian/linda could flag this stuff automatically, which is probably the case. Lars Wirzenius also suggested that I name names so people will know if they're affected. So here are source packages grouped by maintainer. Data is from /var/lib/apt/lists/*_Packages on an i386 sid box. Peter APT Development Team <[EMAIL PROTECTED]>: python-apt Aaron Matthew Read <[EMAIL PROTECTED]>: smlnj Achim Bohnet <[EMAIL PROTECTED]>: digikamimageplugins, libkexif, libkipi Adam Majer <[EMAIL PROTECTED]>: rake Adeodato Simó <[EMAIL PROTECTED]>: amarok Adriaan Peeters <[EMAIL PROTECTED]>: sipcalc Adrian Bridgett <[EMAIL PROTECTED]>: xmove Al Stone <[EMAIL PROTECTED]>: libcoyotl, qprof Alastair McKinstry <[EMAIL PROTECTED]>: lcov Alberto Gonzalez Iniesta <[EMAIL PROTECTED]>: sing Alexandre Fayolle <[EMAIL PROTECTED]>: python-xml Alexandre Pineau <[EMAIL PROTECTED]>: ire Alexei Kaminski <[EMAIL PROTECTED]>: calcoo Andreas Rottmann <[EMAIL PROTECTED]>: python-crypto, zinf Andrew Lau <[EMAIL PROTECTED]>: openexr, tsclient Anthony Fok <[EMAIL PROTECTED]>: cjk-latex, freetype, tochnog Antti-Juhani Kaijanaho <[EMAIL PROTECTED]>: grep-dctrl Arnaud Vandyck <[EMAIL PROTECTED]>: argouml Artem Chuprina <[EMAIL PROTECTED]>: xxkb Arthur Korn <[EMAIL PROTECTED]>: devfsd, iacd Aurelien Jarno <[EMAIL PROTECTED]>: camstream, keybled, kid3, kwave, myphpmoney Baruch Even <[EMAIL PROTECTED]>: chktex Bas Zoetekouw <[EMAIL PROTECTED]>: bibcursed, freesci Bastian Kleineidam <[EMAIL PROTECTED]>: libpam-mount, linkchecker Bdale Garbee <[EMAIL PROTECTED]>: amanda Ben Burton <[EMAIL PROTECTED]>: kdbg, kdeedu Benjamin Drieu <[EMAIL PROTECTED]>: xbvl Benjamin Mako Hill <[EMAIL PROTECTED]>: mairix Bill Allombert <[EMAIL PROTECTED]>: flwm, gap-gdat Bradley Bell <[EMAIL PROTECTED]>: bakery-gnomeui2.0, bakery2.0, bakery2.3 Branden Robinson <[EMAIL PROTECTED]>: twofish Brent A. Fulgham <[EMAIL PROTECTED]>: nana Brian Bassett <[EMAIL PROTECTED]>: blogtk Brian R Furry <[EMAIL PROTECTED]>: stars Brian Sutherland <[EMAIL PROTECTED]>: schoolbell Bruce Walker <[EMAIL PROTECTED]>: ax25-apps Bruno Rodrigues <[EMAIL PROTECTED]>: libapache-mod-security Cajus Pollmeier <[EMAIL PROTECTED]>: nsca Camm Maguire <[EMAIL PROTECTED]>: lam Celso González <[EMAIL PROTECTED]>: ap-utils Chad Walstrom <[EMAIL PROTECTED]>: cheetah Chip Salzenberg <[EMAIL PROTECTED]>: libnet-ftpserver-perl Chris Butler <[EMAIL PROTECTED]>: libcgicc Chris Halls <[EMAIL PROTECTED]>: ayttm Chris Lawrence <[EMAIL PROTECTED]>: reportbug Chris Waters <[EMAIL PROTECTED]>: tcllib Christian Bayle <[EMAIL PROTECTED]>: gatos Christian Bayle <[EMAIL PROTECTED]>: libjfreechart-java, libjfreereport-java Christian Kurz <[EMAIL PROTECTED]>: tinycdb Christophe Prud'homme <[EMAIL PROTECTED]>: arpack Clément Stenac <[EMAIL PROTECTED]>: spong Colin Watson <[EMAIL PROTECTED]>: db1-compat, groff, libcgic Cosimo Alfarano <[EMAIL PROTECTED]>: torch3 Cédric Delfosse <[EMAIL PROTECTED]>: boa-constructor, drpython, tcpick Dafydd Harries <[EMAIL PROTECTED]>: alexandria Daigo Moriwaki <[EMAIL PROTECTED]>: tdiary Dan Korostelev <[EMAIL PROTECTED]>: rhythmbox-applet Daniel Baumann <[EMAIL PROTECTED]>: micro-inetd, thttpd Daniel Bonniot <[EMAIL PROTECTED]>: nice Daniel Gubser <[EMAIL PROTECTED]>: uptimed Daniel Kobras <[EMAIL PROTECTED]>: manpages-de, muse Daniel Schepler <[EMAIL PROTECTED]>: qtads David A. van Leeuwen <[EMAIL PROTECTED]>: tclex David Coe <[EMAIL PROTECTED]>: gpart David I. Lehn <[EMAIL PROTECTED]>: gst-editor, mpeg2dec David Martínez Moreno <[EMAIL PROTECTED]>: k3d David Moreno Garza <[EMAIL PROTECTED]>: gxmms David N. Welton <[EMAIL PROTECTED]>: tdom Davide Puricelli (evo) <[EMAIL PROTECTED]>: chicken, gnome-alsamixer, libnet-ldap-perl Debian Adduser Developers <[EMAIL PROTECTED]>: adduser Debian Berkeley DB Maintainers <[EMAIL PROTECTED]>: db2, db4.1, db4.2, db4.3 Debian Java Mailing List : java-common Debian Java Maintainers <[EMAIL PROTECTED]>: libcommons-dbcp-java, libcommons-lang-java, libcommons-modeler-java, libgef-java, libxerces2-java Debian Nagios Maintainer Group <[EMAIL PROTECTED]>: nagios Debian OCaml Maintainers : bibtex2html, cryptokit, hevea Debian Octave Group <[EMAIL PROTECTED]>: matwrap Debian OpenOffice Team : dmake, neon0.23, openoffice.org, openoffice.org-sdk Debian Perl Group <[EMAIL PROTECTED]>: libalias-perl, soap-lite Debian QA Group <[EMAIL PROTECTED]>: blootbot, fdutils, ic35link, libapache-auth-ldap, middleman, sfio, zed Debian QEMU Team <[EMAIL PROTECTED]>: q
Re: Bug#302138: incorrect Description line wrapping with bullet lists
On Wed, Mar 30, 2005 at 03:54:36AM -0600, Peter Samuelson wrote: > > [Peter Samuelson] > > I'd like to file a mass bug for these, but it's on the order of 583 > > binary packages in 430 source packages, so I obviously want to get > > some feedback first. > > Jeroen van Wolffelaar pointed out to me that 430 source packages is a > bit much for a mass bug, especially if lintian/linda could flag this > stuff automatically, which is probably the case. > > Lars Wirzenius also suggested that I name names so people will know if > they're affected. So here are source packages grouped by maintainer. > Data is from /var/lib/apt/lists/*_Packages on an i386 sid box. It seems like this list has a lot of false positives, take for example php-mail-mime: | Description: PHP PEAR module for creating and decoding MIME messages | Provides classes to deal with creation and manipulation of mime messages: | . | * mime.php: Create mime email, with html, attachments, embedded images | etc. | * mimePart.php: Advanced method of creating mime messages. | * mimeDecode.php - Decodes mime messages to a usable structure. | * xmail.dtd: An XML DTD to acompany the getXML() method of the decoding | class. | * xmail.xsl: An XSLT stylesheet to transform the output of the getXML() | method back to an email It's manually word-wrapped, because otherwise it'd overflow fixed-width terminal displays. That's the whole point of double-space indenting a part of the description. Ideally, all packaging tools would support some kind of very simple markup language to support enumerations in a sane way, but that's a long-term project. So, I object to this massfiling. --Jeroen -- Jeroen van Wolffelaar [EMAIL PROTECTED] (also for Jabber & MSN; ICQ: 33944357) http://Jeroen.A-Eskwadraat.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: duplicates of fonts in some packages
Le Tue, 29 Mar 2005 18:45:01 +0200, Bartosz Fenski aka fEnIo a écrit : > Hello. > > I'm packaging adesklets stuff, and it cames with Vera.ttf font included. > We've got this font in ttf-bitstream-vera package, so I was wondering if is > it ok to duplicate it, since some packages are doing it already. > > At least that's something what I got after `apt-file search Vera.ttf`. > wesnoth-data and epplets are not a case cause they using symlink to the > font from ttf-bitstream-vera and depend on it. > > But widelands-data has its own copy. In addition its copyright file doesn't > mention about different license for this font than for the rest of package. > > I assume that symlink is a good way (tm) for such situations, and that > widelands is buggy, but I'm here to ensure myself and maybe others ;) > > Also maybe writing some script for finding such duplicates would be > reasonable, it could in addition finds conflicting files in other packages, > but that's only idea ;) It looks like a use case for defoma. You can register font or appplication to defoma which then provide some kinds of fonts to the application (dfontmgr provide a visual view on that). This is used for example by ghostrcipt (the print core) . Maybe fontconfig could be used too (though it is only a font registrar). I don't think a recommand to the wanted font package would hurt. However font should not be in application package. There is no font policy per se but at least the policy have a short notice about font usable by the X system being packaged separately (i don't know to which extend this apply here). Well i really hope i would have definitive guidelines about that, My opinion (i am not even DD) is that this is a good practice : fonts are updated and have bugs. I prefer having people who care about fonts maintaining them. (it would be like having the usefull man pages in unrelated packages ... well some does it too :) Regards Alban -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#301892: ITP: cuetools -- tools for manipulating CUE/TOC files
Le Tue, 29 Mar 2005 10:10:06 +0100, David Pashley a écrit : > What are CUE and TOC files? What are they used for? It would be useful > if you say a little bit more about them. Well i do not know if one can define CUE file shortly . This is like "ar" file but for cdroms "images" (not in the iso meaning, the raw image). This enables to store on disk what we want on the cdrom when we mix different type of data type on the medium. It could be a mix of iso9660, audio, video ... Kudos to the one who manage to explain it in a sentence :) Well i may be plain wrong as this talk about TOC too which i though where part of rockridge ... This is obviously for disk at once burn. Won't be of any use for sao. Alban -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#302138: incorrect Description line wrapping with bullet lists
[Jeroen van Wolffelaar] > It seems like this list has a lot of false positives, take for example > php-mail-mime: > > | Description: PHP PEAR module for creating and decoding MIME messages > | Provides classes to deal with creation and manipulation of mime messages: > | . > | * mime.php: Create mime email, with html, attachments, embedded images > | etc. I still think the "etc." should not be indented. Let the tools word-wrap it, rather than having the maintainer guess how wide everyone's terminal will be. But that is, perhaps, a point on which reasonable people can disagree - not least because my suggestion makes 'apt-cache show' a little bit less pretty. Omitting the check for forced word-wrapping in bullets cuts down the list of offenders drastically. The following are source packages that actually display _incorrectly_ in dselect / aptitude because bullet points incorrectly word-wrap back to the previous line. (I hand-checked this list for false positives, so it should be mostly fair.) Adriaan Peeters <[EMAIL PROTECTED]>: sipcalc Bruno Rodrigues <[EMAIL PROTECTED]>: libapache-mod-security Cajus Pollmeier <[EMAIL PROTECTED]>: nsca Christophe Prud'homme <[EMAIL PROTECTED]>: arpack Cosimo Alfarano <[EMAIL PROTECTED]>: torch3 Daniel Gubser <[EMAIL PROTECTED]>: uptimed David Moreno Garza <[EMAIL PROTECTED]>: gxmms Debian Berkeley DB Maintainers <[EMAIL PROTECTED]>: db4.1 Debian Nagios Maintainer Group <[EMAIL PROTECTED]>: nagios Debian Perl Group <[EMAIL PROTECTED]>: soap-lite Eduard Bloch <[EMAIL PROTECTED]>: pdfjam, ppscsi Free Ekanayaka <[EMAIL PROTECTED]>: mcp-plugins GOTO Masanori <[EMAIL PROTECTED]>: ttf-mikachan Jean-Michel Kelbert <[EMAIL PROTECTED]>: k3b, testdisk Joe Wreschnig <[EMAIL PROTECTED]>: pmp-common Joerg Jaspert <[EMAIL PROTECTED]>: lg-issue104, lg-issue105, lg-issue106, lg-issue107, lg-issue109 Joshua Kwan <[EMAIL PROTECTED]>: ircd-hybrid Matthias Urlichs <[EMAIL PROTECTED]>: libvideo-capture-v4l-perl Michael Schiansky <[EMAIL PROTECTED]>: mp3c Otavio Salvador <[EMAIL PROTECTED]>: graveman Philipp Meier <[EMAIL PROTECTED]>: jetty Robert Millan <[EMAIL PROTECTED]>: ltsp-utils Ross Peachey <[EMAIL PROTECTED]>: libgetopt-declare-perl Steinar H. Gunderson <[EMAIL PROTECTED]>: libhttp-dav-perl Stephan Helma <[EMAIL PROTECTED]>: ude Stephen Quinney <[EMAIL PROTECTED]>: libclass-dbi-pager-perl Turbo Fredriksson <[EMAIL PROTECTED]>: libroxen-adbanner signature.asc Description: Digital signature
Re: Bug#302138: incorrect Description line wrapping with bullet lists
On Wed, Mar 30, 2005 at 04:42:24AM -0600, Peter Samuelson wrote: > Omitting the check for forced word-wrapping in bullets cuts down the > list of offenders drastically. The following are source packages that > actually display _incorrectly_ in dselect / aptitude because bullet > points incorrectly word-wrap back to the previous line. (I > hand-checked this list for false positives, so it should be mostly > fair.) Filing bugs for those 30-something packages sounds reasonable to me, as they cause wrong display in almost all situations. --Jeroen -- Jeroen van Wolffelaar [EMAIL PROTECTED] (also for Jabber & MSN; ICQ: 33944357) http://Jeroen.A-Eskwadraat.nl
Re: Should Debian use lsb init-functions?
Le Tue, 29 Mar 2005 00:06:19 -0600, Ron Johnson a écrit : > On Tue, 2005-03-29 at 06:31 +0200, Alban Browaeys wrote: >> Le Tue, 29 Mar 2005 01:09:55 +0200, Jeroen van Wolffelaar a écrit : >> >> > On Mon, Mar 28, 2005 at 02:24:03PM +0200, Wouter Verhelst wrote: >> >> For the record, it is not true that there is no logging of initscripts. >> >> The logging is perhaps not enabled by default and it is perhaps not >> >> detailed to the extent as suggested in the bugreport, but by running >> >> >> >> echo 'BOOTLOGD_ENABLE=Yes' > /etc/default/bootlogd >> >> >> >> one can enable initscript logging to /var/log/boot, which will show >> >> everything that was sent to the console during bootup (excluding kernel >> >> messages). >> > >> > *blink*, wow... why isn't this like on by default, and the package in >> > question installed by default? >> >> well because if you boot in single user mode it will log all your root >> session for example. > > Sounds like a good thing to me! > well that was a bit short so to respect mike works: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=213028 On 2004.04.04 21:26, Greg Wooledge wrote: > You wouldn't have to hack /sbin/sulogin itself. All you would have > to do is add a line to /etc/inittab right *before* the sulogin, which > triggers only in single-user mode: Sure, but that means editting /etc/inittab in postinst. I don't disagree, but there is a bug open against sysvinit that asks for inittab being a conffile which means postinst cannot edit it. Besides, I've decided bootlogd sucks anyway. It would be much better if /etc/init.d/rc simply started the scripts in /etc/rc?.d directories through a script(1) like wrapper. The wrapper would write to /var/log/boot.log directly if it was writable. Otherwise it would connect to a bootlogd-like in-memory buffer process through a UNIX socket or pipe, spawning it if it didn't run yet. Much less fragile. Mike. This looks great in my opinion (i always agree with upstream :) no kidding ). Much like dmesg. I feel showing verbose message is good only that ojn current best one have to be superman to follow the flood ! Alban -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#301892: ITP: cuetools -- tools for manipulating CUE/TOC files
Alban Browaeys <[EMAIL PROTECTED]> wrote: > Le Tue, 29 Mar 2005 10:10:06 +0100, David Pashley a écrit : > >> What are CUE and TOC files? What are they used for? It would be useful >> if you say a little bit more about them. > > Well i do not know if one can define CUE file shortly . This is like "ar" > file but for cdroms "images" (not in the iso meaning, the raw image). > This enables to store on disk what we want on the cdrom when we mix > different type of data type on the medium. > > It could be a mix of iso9660, audio, video ... > > Kudos to the one who manage to explain it in a sentence :) You don't need to explain it so that everybody understands the format. It should be sufficient to say as much as will allow to decide whether the package is useful for me, or not. What about: , | cuetools is a set of programs that are useful for manipulating CD/DVD | image files in CUE format and Table of Contents (toc) files. The CUE | format is used for mixing different data types on one medium (iso9660, | audio, video,...). The package includes these utilities: | |- cueconvert: convert between CUE and TOC formats |- cuebreakpoints: print the breakpoints from a CUE or TOC file |- cueprint: print disc and track information for a CUE or TOC file | | It can also be used to split a large audio file into many | small files according to a CUE or TOC. ` Regards, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer
Re: Development files for manipulating Debian packages
* "Ivan Kirchev" | Does Debian package management suite provide C APIs for | easier program manipulation of .deb files? No, dpkg does not provide any library you can use, yet. It's on the list of features planned. -- Tollef Fog Heen,''`. UNIX is user friendly, it's just picky about who its friends are : :' : `. `' `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
dpatch and patching debian/rules
It seems tha dpatch cannot be trivially used to patch debian/rules when the patch target is called implicitly. Note that it works if I invoke build and then binary separately. If I invoke binary, which depends on build, the patches are applied, but the debian/rules file is already read and patches do not take effect. I am not sure if this is a known problem, I could not find information on it. I am not sure how this could be fixed. Or am I doing something wrong? -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft <[EMAIL PROTECTED]> : :' :proud Debian developer, admin, user, and author `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver! military justice is to justice what military music is to music. -- groucho marx signature.asc Description: Digital signature
Re: dpatch and patching debian/rules
On Wed, 30 Mar 2005, martin f krafft wrote: > It seems tha dpatch cannot be trivially used to patch debian/rules > when the patch target is called implicitly. Note that it works if > I invoke build and then binary separately. If I invoke binary, which > depends on build, the patches are applied, but the debian/rules file > is already read and patches do not take effect. > > I am not sure if this is a known problem, I could not find > information on it. I am not sure how this could be fixed. > > Or am I doing something wrong? Well, I had never heard of anyone crazy enough to patch debian/rules at runtime... You're the first. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#301892: ITP: cuetools -- tools for manipulating CUE/TOC files
On Mar 30, 2005 at 12:38, Frank Küster praised the llamas by saying: > Alban Browaeys <[EMAIL PROTECTED]> wrote: > > > Le Tue, 29 Mar 2005 10:10:06 +0100, David Pashley a écrit : > > > >> What are CUE and TOC files? What are they used for? It would be useful > >> if you say a little bit more about them. > > > > Well i do not know if one can define CUE file shortly . This is like "ar" > > file but for cdroms "images" (not in the iso meaning, the raw image). > > This enables to store on disk what we want on the cdrom when we mix > > different type of data type on the medium. > > > > It could be a mix of iso9660, audio, video ... > > > > Kudos to the one who manage to explain it in a sentence :) > > You don't need to explain it so that everybody understands the format. > It should be sufficient to say as much as will allow to decide whether > the package is useful for me, or not. What about: > > , > | cuetools is a set of programs that are useful for manipulating CD/DVD > | image files in CUE format and Table of Contents (toc) files. The CUE > | format is used for mixing different data types on one medium (iso9660, > | audio, video,...). The package includes these utilities: > | > |- cueconvert: convert between CUE and TOC formats > |- cuebreakpoints: print the breakpoints from a CUE or TOC file > |- cueprint: print disc and track information for a CUE or TOC file > | > | It can also be used to split a large audio file into many > | small files according to a CUE or TOC. > ` > > Regards, Frank That looks much better. Mentioning CD/DVD makes quite a bit of difference if you ask me. -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dpatch and patching debian/rules
On Wed, Mar 30, 2005 at 10:29:41AM -0300, Henrique de Moraes Holschuh wrote: > On Wed, 30 Mar 2005, martin f krafft wrote: > > It seems tha dpatch cannot be trivially used to patch debian/rules > > when the patch target is called implicitly. Note that it works if > > I invoke build and then binary separately. If I invoke binary, which > > depends on build, the patches are applied, but the debian/rules file > > is already read and patches do not take effect. > > > > I am not sure if this is a known problem, I could not find > > information on it. I am not sure how this could be fixed. > > > > Or am I doing something wrong? > > Well, I had never heard of anyone crazy enough to patch debian/rules at > runtime... You're the first. Yeah, patching debian/rules sounds like changing shoes while running the 100 meters track. Michael -- Escape the Java Trap with GNU Classpath! http://www.gnu.org/philosophy/java-trap.html Join the community at http://planet.classpath.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dpatch and patching debian/rules
also sprach Henrique de Moraes Holschuh <[EMAIL PROTECTED]> [2005.03.30.1529 +0200]: > Well, I had never heard of anyone crazy enough to patch > debian/rules at runtime... You're the first. Yeah! We are packaging zope-common from Ubuntu for Debian, patching it with dpatch to make it easier later on for Ubuntu to base its work on Debian, rather than the other way around (even though doko/Ubuntu did most of the work so far). Parts of debian/rules are Ubuntu-specific (e.g. mv README.Debian README.Ubuntu) and we would love to have that removed. So are you saying that we're at a loss here? I guess I can work around it by: build: patch $(MAKE) real-build real-build: /// do whatever but I was wondering if there is a better way... -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft <[EMAIL PROTECTED]> : :' :proud Debian developer, admin, user, and author `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver! "the intellect is not a serious thing, and never has been. it is an instrument on which one plays, that is all." -- oscar wilde signature.asc Description: Digital signature
Re: dpatch and patching debian/rules
On Wed, 30 Mar 2005, martin f krafft wrote: > but I was wondering if there is a better way... I don't think so, other than using makefile includes. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dpatch and patching debian/rules
also sprach Henrique de Moraes Holschuh <[EMAIL PROTECTED]> [2005.03.30.1602 +0200]: > I don't think so, other than using makefile includes. Uh, these are also only read once... -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft <[EMAIL PROTECTED]> : :' :proud Debian developer, admin, user, and author `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver! this space intentionally left occupied. signature.asc Description: Digital signature
Re: dpatch and patching debian/rules
* martin f krafft <[EMAIL PROTECTED]> [050330 14:08]: > It seems tha dpatch cannot be trivially used to patch debian/rules > when the patch target is called implicitly. Just out of curiosity: Why do you need to do this? Yours sincerely, Alexander signature.asc Description: Digital signature
Re: dpatch and patching debian/rules
* Alexander Schmehl <[EMAIL PROTECTED]> [050330 16:09]: > Just out of curiosity: Why do you need to do this? Sorry, was out of synch and just got your other mail. Yours sincerely, Alexander signature.asc Description: Digital signature
Re: dpatch and patching debian/rules
martin f krafft <[EMAIL PROTECTED]> writes:
> Parts of debian/rules are Ubuntu-specific (e.g. mv README.Debian
> README.Ubuntu) and we would love to have that removed.
Why not simply do a ifeq($(DISTRIB),Ubuntu) around that and define DISTRIB
at the top of the Makefile? This way you can use the same debian/rules
for Ubuntu and Debian and don't need to use evil patch systems.
Marc
--
$_=')(hBCdzVnS})3..0}_$;//::niam/s~=)]3[))_$(rellac(=_$({pam(esrever })e$.)4/3*
)e$(htgnel+23(rhc,"u"(kcapnu ,""nioj ;|_- |/+9-0z-aZ-A|rt~=e$;_$=e${pam tnirp{y
V2ajFGabus} yV2ajFGa&{gwmclBHIbus}gwmclBHI&{yVGa09mbbus}yVGa09mb&{hBCdzVnSbus';
s/\n//g;s/bus/\nbus/g;eval scalar reverse #
pgpf4o5XtQWt9.pgp
Description: PGP signature
Add a project to debian
Hello, I am interested in adding a project into the Debian Project and wanted to ask a couple of questions on how to achieve this. After having read the documentations I understood that I needed to apply as a new maintainer (with the appropriate identification process, needing an "advocate" Debian developper) and then find a sponsor that would accept upload the packages for me. If these two steps are performed correctly, this means that my package will be available on the debian repositories (on unstable, until it is considered stable enough to "apply" for testing) ? If this is so, what is approximatively the time between the upload of my package by a sponsor and the actual "distribution" of my package through debian repositories ? Thanks in advance for your help. Alexis Papadopoulos _ FREE pop-up blocking with the new MSN Toolbar - get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: FW: Contact Information
Op di, 29-03-2005 te 11:52 -0700, schreef Annabelle Garcia: > I am sorry to bother you again. I am just following up to see if there > is any way you can direct me to the right contact. Debian is not a company, it is a volunteer-based effort. -- EARTH smog | bricks AIR -- mud -- FIRE soda water | tequila WATER -- with thanks to fortune -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Add a project to debian
On Wed, Mar 30, 2005 at 02:18:28PM +, Alex Papadopoulos wrote: > After having read the documentations I understood that I needed to apply as > a new maintainer (with the appropriate identification process, needing an > "advocate" Debian developper) and then find a sponsor that would accept > upload the packages for me. You don't necessarily have to apply as a new maintainer. > If these two steps are performed correctly, this means that my package will > be available on the debian repositories (on unstable, until it is > considered stable enough to "apply" for testing) ? Yes. Once your sponsor uploads your package (after it has been checked over), your package will initially appear in the unstable archive. > If this is so, what is approximatively the time between the upload of my > package by a sponsor and the actual "distribution" of my package through > debian repositories ? On first upload, a package must await some manual processing by the ftpmasters. There has been a bit of a backlog built up in this area, but at current observations packages are flowing through at a decent rate, so I wouldn't expect your package to sit in the NEW queue for more than a couple of weeks. After that, subsequent uploads of your package should appear on all mirrors in less than a day, although buildd queues might cause this to be delayed a little for some architectures. This is all a bit confusing; there has been a diagram of the way a package floats around posted here recently, do a search for debian package diagram or similar on google. Also, you might be interested in joining the debian-mentors mailing list, where basic packaging and development questions are more usually asked. - Matt signature.asc Description: Digital signature
Re: dpatch and patching debian/rules
also sprach Marc 'HE' Brockschmidt <[EMAIL PROTECTED]> [2005.03.30.1615 +0200]: > Why not simply do a ifeq($(DISTRIB),Ubuntu) around that and define > DISTRIB at the top of the Makefile? This way you can use the same > debian/rules for Ubuntu and Debian and don't need to use evil > patch systems. Ah, this is definitely something to consider. The main reason why I have not looked at such approaches is simply because I did not want to invade on doko right now. The zope-common we are preparing is very much scaled down and really only designed to - get zope-common through NEW before sarge - fix #256615 All the other improvements doko has prepared (awesome job, lemme tell you!) are to be fed into experimental for now. Whether they will make sarge is currently unknown (I hope *not* -- we need to do a lot of testing, and making sarge would mean that sarge takes even longer...). Anyway, thanks Marc for the suggestion. I think I will prepare an updated debian/rules based on this and send it to doko. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft <[EMAIL PROTECTED]> : :' :proud Debian developer, admin, user, and author `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver! "never speak disrespectfully of society. only people who can't get into it do that." -- oscar wilde signature.asc Description: Digital signature
Re: dpatch and patching debian/rules
On Wed, 30 Mar 2005, martin f krafft wrote: > also sprach Henrique de Moraes Holschuh <[EMAIL PROTECTED]> [2005.03.30.1602 > +0200]: > > I don't think so, other than using makefile includes. > > Uh, these are also only read once... Change them BEFORE the ubuntu build. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Add a project to debian
Ok thanks for the quick reply. Another question though that I forgot before, if the sponsor uploads the packages is he automatically the maintainer of the package (because if this is the case, then it means that sponsoring is a very demanding process for him, and makes therefore sponsoring a quite difficult task for me). And by maintaining activally my package is it possible to become allegible for debian developper, being able therefore to upload my packages on my own ? Thanks for the help, any further, more technical-related questions will be posted on debian-mentors... Alexis Papadopoulos _ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Add a project to debian
On Wed, 30 Mar 2005, Alex Papadopoulos wrote: > Ok thanks for the quick reply. Another question though that I forgot > before, if the sponsor uploads the packages is he automatically the > maintainer of the package (because if this is the case, then it means that Yes and no. He is as responsible for the package as the one he is sponsoring, although not all sponsors seem to take this seriously enough. > sponsoring is a very demanding process for him, and makes therefore > sponsoring a quite difficult task for me). Yes, sponsoring properly takes a lot of time. Slightly less than maintaining the package itself, IMHO. > And by maintaining activally my package is it possible to become allegible > for debian developper, being able therefore to upload my packages on my own > ? Yes, after some time. Please read http://nm.debian.org. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Add a project to debian
On Wed, Mar 30, 2005 at 02:30:26PM +, Alex Papadopoulos wrote: > Ok thanks for the quick reply. Another question though that I forgot > before, if the sponsor uploads the packages is he automatically the > maintainer of the package (because if this is the case, then it means that > sponsoring is a very demanding process for him, and makes therefore > sponsoring a quite difficult task for me). Not really. The maintainer of a package is the person listed in the Maintainer: field for that package. The job of a sponsor is a fairly demanding one, though -- you have to carefully check the package over to make sure it is as good as it can be, and doesn't contain any potentially harmful code. It's generally preferred if the sponsor uses the package or is interested in it in some way, so they're more motivated to check the package properly. > And by maintaining activally my package is it possible to become allegible > for debian developper, being able therefore to upload my packages on my own > ? Yes. That is the typical way to become a Debian Developer these days: maintain one or more packages through a sponsor for a little while, so you get experience and confidence, and then apply for NM (New Maintainer) and go from there through the process. - Matt signature.asc Description: Digital signature
Re: dpatch and patching debian/rules
martin f krafft <[EMAIL PROTECTED]> wrote: > also sprach Henrique de Moraes Holschuh <[EMAIL PROTECTED]> [2005.03.30.1529 > +0200]: >> Well, I had never heard of anyone crazy enough to patch >> debian/rules at runtime... You're the first. > > Yeah! > > We are packaging zope-common from Ubuntu for Debian, patching it > with dpatch to make it easier later on for Ubuntu to base its work > on Debian, rather than the other way around (even though doko/Ubuntu > did most of the work so far). There is a way to cause make to re-read a Makefile: Makefile remaking. debian/rules: debian/rules.in $(command that recreates debian/rules) --infile $< --outfile $@ $(command that recreates debian/rules) would somehow check whether it is a Debian build or an Ubuntu build (looking at environment variables, file existense, whatever) and change debian/rules accordingly. And make will reread the file after it has updated it. Regards, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer
Re: Bug#302138: incorrect Description line wrapping with bullet lists
On Wednesday 30 March 2005 05:19 am, Jeroen van Wolffelaar wrote: > Ideally, all packaging tools would support some kind of very simple > markup language to support enumerations in a sane way, but that's a > long-term project. There's room in the description standard for future extensions: quoting Policy, Those containing a space, a full stop and some more characters. These are for future expansion. Do not use them. We can also extend the description format in backwards-compatible ways. So, while a proper markup language would be nice, that doesn't preclude fixing the bullet problem, albeit in a slightly hacky way, NOW. What about this: == A line beginning with two or more spaces, followed by a bullet character and a space, is considered to be an element of a bulleted list. Every succeeding line that begins with N+1 or more spaces, where N is the number of spaces preceding the bullet, is considered to be part of the same bulleted list, and is processed as if N+1 spaces had been stripped from its left margin, with the exception that if the N+2nd character is not a space, the line is formatted as if a leading space were present. (see below) Bullet characters are (maybe) "-", "+", "*", and "o"; the frontend may render them literally or modify their appearence as it deems appropriate. NOTE: it might be a good idea to exclude "o"; I doubt many packages use "o" as a word by itself at the beginning of a literally-formatted line, but it might be a word in some foreign language, which would cause problems once we have translated descriptions. Unfortunately, this would make the format less backwards-compatible. == This means that the current "best practice" for bulleted lists; eg, Description: something with a bulleted list This is a package. It has some features: * A feature. * Another feature. * A feature I felt like continuing onto the next line for some reason * For backwards compatibility, some variation in indentation is OK. will be displayed as expected in all current frontends, while future frontends will treat each of the last two items as a paragraph and word-wrap it accordingly. Lists-within-lists would work like this: Description: something with two bulleted lists This is a package. It has lots of features: * A feature. * Another feature. * A really complicated feature with subfeatures: + Subfeature 1 + Subfeature 2 + Subfeatures can also continue to the next line. . We can also have paragraph separators. * Another feature. The only non-sensibly-rendering thing in legacy frontends would be the literal full-stop, which could be avoided by discouraging the use of multiple-paragraph list items (and really, descriptions shouldn't be that complicated anyway...IMO). Things to note: - Older frontends will render descriptions in this format without any difficulty. - Newer frontends will either automagically detect bulleted lists in older descriptions (all the proper lists that I found in a very small sample would work exactly as expected) or display them literally (the current situation). The worst case would be where the start of a list is literal and its continuation is word-wrapped, but this would come out no worse than the current situation: * A feature * Some other feature but I want you to word-wrap the continuation. All-in-all, I think that this is a nice low-cost way of getting proper bullet support into the frontends. Comments? Daniel -- /--- Daniel Burrows <[EMAIL PROTECTED]> --\ | "You keep on using that word. I do not think | |it means what you think it means." | | -- "The Princess Bride" | \ The Turtle Moves! -- http://www.lspace.org ---/ pgp0DWWR190yA.pgp Description: PGP signature
Re: Bug#302138: incorrect Description line wrapping with bullet lists
On Wednesday 30 March 2005 09:56 am, Daniel Burrows wrote: > A line beginning with two or more spaces, followed by a bullet character > and a space, is considered to be an element of a bulleted list. Every > succeeding line that begins with N+1 or more spaces, where N is the number > of spaces preceding the bullet, is considered to be part of the same > bulleted list, and is processed as if N+1 spaces had been stripped from its > left margin, with the exception that if the N+2nd character is not a space, > the line is formatted as if a leading space were present. (see below) I didn't mention this here, but of course the frontend is expected to pay attention to the quantity of indentation, preserve leading indentation of the bullet, and use this information to figure out sub-list relationships. Daniel -- /--- Daniel Burrows <[EMAIL PROTECTED]> --\ | Hi, I'm a .signature virus! | | Copy me into your .signature to help me spread! | \-- Listener-supported public radio -- NPR -- http://www.npr.org ---/ pgpiTS7knHy0r.pgp Description: PGP signature
Re: Bug#302138: incorrect Description line wrapping with bullet lists
On Wed, Mar 30, 2005 at 09:56:36AM -0500, Daniel Burrows wrote: > Bullet characters are (maybe) "-", "+", "*", and "o"; the frontend may > render them literally or modify their appearence as it deems appropriate. > NOTE: it might be a good idea to exclude "o"; I doubt many packages use "o" > as a word by itself at the beginning of a literally-formatted line, but it > might be a word in some foreign language, I know of at least two such languages. Don't include 'o'. -- .''`. ** Debian GNU/Linux ** | Andrew Suffield : :' : http://www.debian.org/ | `. `' | `- -><- | signature.asc Description: Digital signature
Re: Bug#302138: incorrect Description line wrapping with bullet lists
On Wednesday 30 March 2005 11:44 am, Andrew Suffield wrote: > I know of at least two such languages. Don't include 'o'. Ok, will do. Or, um, not do. Daniel -- /--- Daniel Burrows <[EMAIL PROTECTED]> --\ |Human beings were created by water to transport it uphill. | \- A duck! -- http://www.python.org / pgp2ST4C7IpIO.pgp Description: PGP signature
Re: dpatch and patching debian/rules
#include * martin f krafft [Wed, Mar 30 2005, 04:00:21PM]: > also sprach Henrique de Moraes Holschuh <[EMAIL PROTECTED]> [2005.03.30.1529 > +0200]: > > Well, I had never heard of anyone crazy enough to patch > > debian/rules at runtime... You're the first. > > Yeah! > > We are packaging zope-common from Ubuntu for Debian, patching it > with dpatch to make it easier later on for Ubuntu to base its work > on Debian, rather than the other way around (even though doko/Ubuntu > did most of the work so far). > > Parts of debian/rules are Ubuntu-specific (e.g. mv README.Debian > README.Ubuntu) and we would love to have that removed. That's crazy. Originaly, I wrote svn-buildpackage (former svn-devscripts) for a similar purpose - the "other" Debian package has been imported as pseudo-upstream source and svn tracked the difference between "upstream" versions. Not sure whether this hack still works, I have not beeing used it for months and changed a lot in the scripts. Regards, Eduard. -- Wie gut wäre es, wenn man die Stimmen, anstatt sie zu zählen, wägen könnte. -- Georg Christoph Lichtenberg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dpatch and patching debian/rules
On Wed, 2005-03-30 at 16:56 +0200, Frank Küster wrote: > There is a way to cause make to re-read a Makefile: Makefile remaking. > > debian/rules: debian/rules.in > $(command that recreates debian/rules) --infile $< --outfile $@ > > ... make will reread the file after it has updated it. does that mean that something as simple as debian/rules: patch # nothing or "/bin/true" or "touch debian/rules"? where patch is the target that does the patching should also cause a reread? Perhaps you would also need "build: debian/rules" and/or the substitution of a stamp file for the (presumably) .PHONY patch target? Ian. -- Ian Campbell hmm, lunch does sound like a good idea would taste like a good idea too signature.asc Description: This is a digitally signed message part
Re: dpatch and patching debian/rules
> It seems tha dpatch cannot be trivially used to patch debian/rules > when the patch target is called implicitly. Note that it works if > I invoke build and then binary separately. If I invoke binary, which > depends on build, the patches are applied, but the debian/rules file > is already read and patches do not take effect. > > I am not sure if this is a known problem, I could not find > information on it. I am not sure how this could be fixed. debnest makes it possible to patch debian/rules. > Or am I doing something wrong? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dpatch and patching debian/rules
Ian Campbell <[EMAIL PROTECTED]> wrote: > On Wed, 2005-03-30 at 16:56 +0200, Frank Küster wrote: > >> There is a way to cause make to re-read a Makefile: Makefile remaking. >> >> debian/rules: debian/rules.in >> $(command that recreates debian/rules) --infile $< --outfile $@ >> >> ... make will reread the file after it has updated it. > > does that mean that something as simple as > > debian/rules: patch > # nothing or "/bin/true" or "touch debian/rules"? > > where patch is the target that does the patching should also cause a > reread? If it is "touch debian/rules", then it will be reread; however it will (try to )patch it over and over again. This works: ,[ Makefile ] | all: | echo hello | | Makefile: patch-stamp | touch $@ | | patch-stamp: | patch -p0 < Makefile.patch | touch patch-stamp ` ,[ Makefile.patch ] | --- Makefile.orig 2005-03-30 20:49:16.0 +0200 | +++ Makefile 2005-03-30 20:49:20.0 +0200 | @@ -1,5 +1,5 @@ | all: | - echo hello | + echo goodbye | | Makefile: patch-stamp | touch $@ ` Regards, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer
CALL WwAVE cANCELATION
PLEASE UNSUBSUBSCRIBE ME AS OF TODAY---THANK YOU
Bug#302242: ITP: php4-dbase -- dBase module for php4
Package: wnpp Severity: wishlist Owner: Kim Lundgren <[EMAIL PROTECTED]> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 * Package name: php4-dbase Version : 4.3.10 Upstream Author : The PHP Group <[EMAIL PROTECTED]> * URL : http://www.php.net/ * License : (PHP License, libdbf) Description : dBase module for php4 This package provides a module for accessing dBase databases from PHP scripts. PHP4 is an HTML-embedded scripting language. Much of its syntax is borrowed from C, Java and Perl with a couple of unique PHP-specific features thrown in. The goal of the language is to allow web developers to write dynamically generated pages quickly. - -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.10 Locale: LANG=sv_SE, LC_CTYPE=sv_SE (charmap=ISO-8859-1) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCSxJFkF6u449LbOwRAsXhAJ44s44c9PpWX1+XQMfutR95aSW27gCgiSn1 lLg+Eyb2rlj0/ixuKvim3p4= =ghjw -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Add a project to debian
On Thu, 2005-03-31 at 00:22 +1000, Matthew Palmer wrote: > This is all a bit confusing; there has been a diagram of the way a > package floats around posted here recently, do a search for debian > package diagram or similar on google. http://debian.home.pipeline.com/newdebian2.png HTH Ben -- [EMAIL PROTECTED] - www.seigan.org PGP Key fingerprint = 4309 1C58 5143 AFAC F69E 11CD 76FD 56D4 1223 E387 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Standard description file about maintainer groups
Ola Lundqvist dijo [Mon, Mar 28, 2005 at 10:37:33AM +0200]: > > * Sean Perry [Sun, 27 Mar 2005 18:36:49 -0800]: > > > > > Source: mysource > > > Maintainer: Bob <[EMAIL PROTECTED]> > > > Maintainers: Bob <[EMAIL PROTECTED]>, George <[EMAIL PROTECTED]> > > > > > I left the Maintainer in place to allow for some backwards > > > compatibility. This could be the 'captain' of the project. > > > > Or a list. See the Maintainer field of e.g. lintian, exim4, kde. > > And wrt 'Maintainers', there is 'Uploaders' already. > > A common way is to list the contact address for the group > as maintainer and each person responsible for uploads in Uploaders. > You miss non official Debian developers this way though. In the pkg-perl group, I often list a non-DD as an uploader, even if he cannot formally upload - He is a comaintainer anyway. Greetings, -- Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)1451-2244 / 5554-9450 PGP key 1024D/8BB527AF 2001-10-23 Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Policy for devfs support
On Sat, Mar 26, 2005 at 07:24:05PM +0100, Marco d'Itri wrote: > On Mar 26, Roger Leigh <[EMAIL PROTECTED]> wrote: > > > Is there a project-wide policy for support for devfs (and devfs-style, > > e.g. udev devfs.rules) device naming? > No, but nearly all packages support both conventions. Nearly all... I know an exception: tpconfig 3.1.3-5configure touchpad devices Very quiet upstream and 18 month old binary package in testing :-) Osamu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#302283: ITP: sleepshell -- Sleep dummy shell
Package: wnpp Severity: wishlist Owner: Leonardo Serra <[EMAIL PROTECTED]> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package name: sleepshell Version : 0.0.1-1 Upstream Author : Leonardo Serra <[EMAIL PROTECTED]> URL : http://www.mariovaldez.net/software/sleepshell/ License : GPL Description : Sleep dummy shell This is a simple do-nothing, sleep-forever program that can be used as a login shell to keep the connection open but without interactive shell. You can use it to create SSH accounts for users who will only use them for SSH-tunneling; to create an encrypted tunnel to your servers. I make a package and put in http://www.leoserra.uaivip.com.br/debian/sleepshell/ thanks leo serra - -- System Information: Debian Release: 3.1 APT prefers experimental APT policy: (990, 'experimental'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.10-1-686 Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCS1AQidffdjWZJQERAiZrAKCA4lF86Qe5nECe42vqx86xEP79CwCeP3Cr zlSRmyRO4THiLOm/TkBbwyI= =Of7N -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#302283: ITP: sleepshell -- Sleep dummy shell
On Wed, Mar 30, 2005 at 10:19:12PM -0300, Leonardo Serra wrote: > You can use it to create SSH accounts for users who will > only use them for SSH-tunneling; to create an encrypted > tunnel to your servers. Or you can use the -N option to OpenSSH. - Matt signature.asc Description: Digital signature
Re: Standard description file about maintainer groups
Quoting Ola Lundqvist ([EMAIL PROTECTED]): > A common way is to list the contact address for the group > as maintainer and each person responsible for uploads in Uploaders. > You miss non official Debian developers this way though. This is the way d-i packages are handled. This is also the way I have chosen for the shadow package maintenance. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: intend-to-implement: script to obtain Debian Source
* George Danchev | I second suggestion given at #250202 and like to see "unpacked" and | "patched" targets to hit Policy 4.8. If so, it should be «unpack» and «patch» to match the build and install targets. -- Tollef Fog Heen,''`. UNIX is user friendly, it's just picky about who its friends are : :' : `. `' `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: intend-to-implement: script to obtain Debian Source
* Lars Wirzenius | su, 2005-03-27 kello 09:01 +0200, George Danchev kirjoitti: | | > I second suggestion given at #250202 and like to see "unpacked" | > and "patched" targets to hit Policy 4.8. | | I hear that Adam Heath (doogie for those on IRC) has been working on a | new source package format that will make tarball-within-tarball sources | obsolete and has native support for multiple patches and cures for other | ailments. If this works, and I suspect it will, then "unpack" and | "patch" targets will also be obsolete. Personally, I think this will be | a good thing. TTBOMK, he hasn't discussed this with the dpkg maintainer, nor has he made his code public. -- Tollef Fog Heen,''`. UNIX is user friendly, it's just picky about who its friends are : :' : `. `' `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dpatch and patching debian/rules
[martin f krafft] > Parts of debian/rules are Ubuntu-specific (e.g. mv README.Debian > README.Ubuntu) and we would love to have that removed. The DISTRIB thing can be implemented quite easily without include files or anything. Just say: DISTRIB := $(shell something-that-prints-DEBIAN-or-UBUNTU) ifeq($(DISTRIB),UBUNTU) ... else ... endif signature.asc Description: Digital signature
Re: NEW handling: About rejects, and kernels
* Thomas Bushnell BSG | Huh? I'm not saying I pretend it isn't there. Do I want to modify | the source code? No, because there's nothing I could do with it if I | could. Sure there is, like, reprogramming the image shown when your computer boots. -- Tollef Fog Heen,''`. UNIX is user friendly, it's just picky about who its friends are : :' : `. `' `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: intend-to-implement: script to obtain Debian Source
On Thu, 31 Mar 2005 08:54:01 +0200, Tollef Fog Heen uttered > TTBOMK, he hasn't discussed this with the dpkg maintainer, nor has he > made his code public. > Er, Adam Heath has made plenty of uploads of dpkg, and is listed as an Uploader. Cheers, -- Steve I may be love's bitch, but at least I'm man enough to admit it. - Spike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dpatch and patching debian/rules
also sprach Peter Samuelson <[EMAIL PROTECTED]> [2005.03.31.0906 +0200]: > DISTRIB := $(shell something-that-prints-DEBIAN-or-UBUNTU) Rene told me about lsb-release. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft <[EMAIL PROTECTED]> : :' :proud Debian developer, admin, user, and author `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver! "when women love us, they forgive us everything, even our crimes; when they do not love us, they give us credit for nothing, not even our virtues." -- honoré de balzac signature.asc Description: Digital signature
Bug#302235: ITP: authconfig -- Text/Graphical tool for setting up NIS, LDAP, kerberos and shadow passwords.
Package: wnpp Severity: wishlist Owner: Ghe Rivero <[EMAIL PROTECTED]> * Package name: authconfig Version : 4.6.11 Upstream Author : Nalin Dahyabhai <[EMAIL PROTECTED]> * URL : http://fedora.redhat.com/projects/config-tools/authconfig.html * License : GPL Description : Text/Graphical tool for setting up NIS, LDAP, kerberos and shadow passwords. Authconfig is a terminal/graphical mode program which can configure a workstation to use shadow (more secure) passwords. Authconfig can also configure a system to be a client for certain networked user information and authentication schemes. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: alpha Kernel: Linux 2.6.10-1-smp Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#302278: ITP: libuser-identity-perl -- manages different identities/roles used for email
Package: wnpp
Severity: wishlist
Owner: Gunnar Wolf <[EMAIL PROTECTED]>
* Package name: libuser-identity-perl
Version : 0.90
Upstream Author : Mark Overmeer <[EMAIL PROTECTED]>
* URL : http://perlovermeer.net/userid/
* License : GPL + artistic
Description : manages different identities/roles used for email
The "Mail::Identity" object contains the description of role played by
a human when sending e-mail. Most people have more than one role these
days: for instance, a private and a company role with different e-mail
addresses.
An "Mail::Identity" object combines an e-mail address, user description
("phrase"), a signature, pgp-key, and so on. All fields are optional,
and some fields are smart. One such set of data represents one role.
"Mail::Identity" is therefore the smart cousine of the Mail::Address
object.
This module is required by the new upstream version of libmail-box-perl,
already in the archive.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-lafa
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]
