Re: Bug#524787: ITP: unicorn -- Drivers and applications for the Bewan ADSL PCI ST and USB modems
Nick Leverton wrote: > I'm thinking of renaming the binary package as unicorn-utils for the > next upload to make this clearer. please use the -tools suffix which his used by most userland tool packages for modules. -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: daniel.baum...@panthera-systems.net Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: debian and lilypond 2.12
I don't object to a suitable Debian developer who wants to take over maintenance of lilypond. They should contact me directly. Thomas -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: The ‘read -r’ bashism.
Charles Plessy writes: >> > checkbashisms' output: >> > > possible bashism in >> > > ./usr/share/EMBOSS/jemboss/utils/install-jemboss-server.sh line 607 >> > > (should >> > > be read [-r] variable): >> > > read > > I would like to forward this Upstream, but I have no clue of what the problem > is, and how important it is. I have read > ‘https://wiki.ubuntu.com/DashAsBinSh’, > but found nothing there. Can somebody send me a pointer to some documentation? My guess (although I am not by any means authoritative on this) is that this is just saying that writing "read" without supplying an argument is a bashism. In bash, "read" by itself reads a line into a variable named REPLY, but the standard requires a variable name to be supplied. Perhaps the fix is as simple as changing read to read REPLY. You can read about bash's "read" command by typing "help read" at a bash prompt. You can read the POSIX standard for the "read" command at http://www.opengroup.org/onlinepubs/009695399/utilities/read.html -- Ben Pfaff http://benpfaff.org -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: DEP 5 and directory/file names with spaces
On Tue, Jun 09, 2009 at 04:13:13PM +0200, Giacomo A. Catenazzi wrote:
> Manoj Srivastava wrote:
> >On Tue, Jun 09 2009, Lars Wirzenius wrote:
> >
> >
> >>Some highlights:
> >>
> >>* two carriage return chars (\r)
> >>* one escape char
> >>* 5431 spaces
> >>* 1 double quotes (")
> >>* 98 single quotes (')
> >>* 64 asterisks (*)
> >>* 524 commas
> >>* 3 backslashes
> >>* 51601 percent chars (%)
> >
> >No newlines, eh? Seems like the one glob per line wins.
>
> Also no tabs, so we can keep horizontal and vertical split of pathnames.
>
> But what glob rule?
> One simple:
> - * as shell glob
> - \\ (3 cases)
> - \* (64 cases)
>
> but how to specify \r (2 cases), \e (one case) and the non-7 bit ASCII (793
> cases)?
> (surely some sequences are non UTF-8 compatible, e.g. 3 0xFE)
Maybe it would be a good idea to contact the upstream of packages with
non-utf8 compatible characters in their filenames and gently suggest a
modified naming policy?
This might apply to some other of the more complicated characters too,
at least the more uncommon ones (for instance, according to the above
statistics there's only one file with a double qute, so it'd make sense
to have it renamed, similarly for the 3 backslashes).
Regards: David
--
/) David Weinehall /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) http://www.acc.umu.se/~tao/(/ Beautiful hoar-frost (/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
The ‘read -r ’ bashism.
Dear all, in the ‘checkbashisms’ bugs of a package I work on, there is the following: > > checkbashisms' output: > > > possible bashism in > > > ./usr/share/EMBOSS/jemboss/utils/install-jemboss-server.sh line 607 > > > (should > > > be read [-r] variable): > > > read I would like to forward this Upstream, but I have no clue of what the problem is, and how important it is. I have read ‘https://wiki.ubuntu.com/DashAsBinSh’, but found nothing there. Can somebody send me a pointer to some documentation? Have a nice day, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Xen - Source?
Michael Shuler wrote: > You're right. Ben pointed to the xen patch directory in the linux-2.6 > source package in his reply - the package build should not fetch the > repo. I just spoke up (probably incorrectly, without asking for more > info) to help with what I thought he was seeing. > OK, fair enough, glad that's cleared up. Cheers, David. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
How to package a network connectivity daemon "the Debian way"
Hi, after years being an user occasionally packaging small things in a rather quick-and-dirty way I have recently taken my first attempt to build a package that is supposed to be used by a larger crowd (and, eventually, end up in the Debian repository some day). The package works fine so far, but there are a few questions on how to structure it. The application to be packaged is isatapd by Sascha Hlusiak (http://saschahlusiak.de/linux/isatap.htm), a small userspace daemon that aids in autoconfiguring RFC5214 (Intra-Site Automatic Tunnels) tunnels in the Linux kernel. In the end, that's pretty much a standard proto-41 IPv6-in-IPv4 tunnel with a special addressing structure as outlined by the RFC. I have put the first try of packaging into the Ubuntu Launchpad PPA at https://launchpad.net/~berni/+archive/ppa (actually, it was developed on Debian Lenny, but my testers wanted amd64 binaries). It's not fully conforming Debian standards yet (copyright file is wrong for example). The main question is on how to start the daemon. Generally, the package should be safe to run out of the box. It will only attempt configuration if it can resolve the unqualified hostname 'isatap', and it will only configure addresses/routes and thus provide any sort of connectivity to the system if it could actually speak to a ISATAP-compliant router on the other side of the tunnel (determined by said hostname). The only drawback is that due to the way ISATAP works in the linux kernel there is no way to depref ISATAP in case other (native?) IPv6 connectivity is available. That could cause disrupted (if return traffic is sent to the wrong interface) or suboptimal (tunneled instead of native) IPv6 connectivity. At the moment I can think of five ways a) Initscript sourcing /etc/default/isatapd with RUN=yes by default, started at boot with update-rc.d. Pro/Contra: people have a chance/hazard to get IPv6 out of the box without configuring anything. They might as well not notice that they need to configure something if the hostname/domain is non-standard b) Initscript sourcing /etc/default/isatapd with RUN=yes, but not started at boot. Pro: people can choose to run it manually or start it on boot on their own agenda Contra: does not give IPv6 without manual intervention c) Initscript sourcing /etc/default/isatapd with RUN=no by default, started at boot with update-rc.d. Pro: people have to review the "config file". Contra: cannot start it manually using the initscript c1) use RUN=yesno and RUN_ON_BOOT=yesno and check in initscript whether we're booting. How? d) get rid of the initscript, plug it into ifupdown and configure the parameters in /etc/network/interfaces. I'd consider this the Debian way, but how does this cooperate with NetworkManager and Co? e) don't provide any scripts, have the user read up and start it manually What would be the preferred way? The second question is about reloading. On a SIGHUP the daemon releases address/routers, redoes the DNS query, then requeries the upstream ISATAP router. At the moment that behaviour is linked to the 'reload'-initscript parameter. However, it does not really reload its configuration (which are the daemon parameters in /etc/default/isatapd). Is this too confusing for the user? Should this be renamed (how)? Is this something that should be in the init script at all? Last but not least, although isatapd periodically refreshes the reachability it might end up temporarily blackholing IPv6 connectivity if IPv4 changes or is shutdown. Would it make sense to package a script in /etc/network/if-down.d and /etc/ppp/ip-down.d that sends a SIGHUP to the daemon when any interface goes down? All comments are appreciated. Also all tips on how to improve the current packaging are welcome. Thanks, Bernhard -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Xen - Source?
On 06/09/2009 02:59 PM, David Claughton wrote: > Michael Shuler wrote: >> On 06/09/2009 11:49 AM, Andreas wrote: >>> Installing it (make), it downloads the binary of the hypervisor! >>> "Cloning http://xenbits.xensource.com/linux-2.6.18-xen.hg " # >>> (downloading) >> This is an incorrect understanding of that download step - it is a >> *source* download from the upstream mercurial repository: > > Are you saying the source package does not actually contain the source > code, but is just a framework for downloading the actual source? > > If so, this seems unusual to me. AIUI it's normal practice for a source > package to contain a local copy of the source tree because Debian cannot > make the assumption that xenbits.xensource.com will always be there. You're right. Ben pointed to the xen patch directory in the linux-2.6 source package in his reply - the package build should not fetch the repo. I just spoke up (probably incorrectly, without asking for more info) to help with what I thought he was seeing. Kind Regards, Michael -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#532540: ITP: libasterisk-config-perl -- configuration read and write module for the Asterisk PBX
Package: wnpp Severity: wishlist X-Debbugs-CC: debian-devel@lists.debian.org Owner: Tzafrir Cohen * Package Name: libasterisk-config-perl Version : 0.97 Upstream Author : Sun Bing * URL : http://search.cpan.org/dist/Asterisk-config/ * License : GPL2 * Programming Lang: Perl * Description : configuration read and write module for the Asterisk PBX perl module for parsing and rewirting the configuration files of the Asterisk PBX. Will be packaged in the pkg-voip team. Already available at svn://svn.debian.org/pkg-voip/trunk/libasterisk-config-perl/trunk http://svn.debian.org/viewsvn/pkg-voip/libasterisk-config-perl/ -- Tzafrir Cohen | tzaf...@jabber.org | VIM is http://tzafrir.org.il || a Mutt's tzaf...@cohens.org.il || best ICQ# 16849754 || friend -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Xen - Source?
On Tue, 2009-06-09 at 18:49 +0200, Andreas wrote: > Hallo everybody! > > Xen is distributed with Debian (main) > > Seems the source-package doesn't contain the code of the hypervisor. Which package? > Also /lib/modules/2.6-686/kernel/arch/xen/i386/mm/hypervisor.c is not > included. No, that's not where we install sources. > Installing it (make), it downloads the binary of the hypervisor! > "Cloning http://xenbits.xensource.com/linux-2.6.18-xen.hg " # > (downloading) Use dpkg-buildpackage to build Debian packages. Running "make" directly is not guaranteed to do the right thing. > So where do I find the source of the xen-Hypervisor (running below the > linux-kernel)? - Or: why could it be distributed with Debian? The hypervisor is in the xen-3 source package: apt-get source xen-3 The Linux dom0 code is in the linux-2.6 source package (as patches in the subdirectory debian/patches/features/all/xen/): apt-get source linux-2.6 cd linux-2.6-* debian/rules setup Ben. -- Ben Hutchings Everything should be made as simple as possible, but not simpler. - Albert Einstein signature.asc Description: This is a digitally signed message part
Re: apt-get wrapper for maintaining Partial Mirrors
On Tuesday 09 June 2009 13:14:53 sanket agarwal wrote: > Hi all, > > We all know that there are various distro's that build around Debian. > I had an idea in mind whereby the task of making mirrors for personal > distributions can be automated. This can be stated as: if a person > wants to keep a customised set of packages for usage with the > distribution, the tool should be able to develop dependencies, fetch > packages, generate appropriate documentation and then create the > corresponding directory structure in the target mirror! The task can > be extended to include packages which are currently not under one of > the standard mirrors! > > I think the tool can have immense utility in helping people automate > the task of mantaining the repositories. Suggestions, positive and > negative are invited. > > I have not included the impl details as I would first like to evaluate > the idea at a feasibility and utility level. I have been working on this idea myself for quite a while, but I haven't messed with the problem recently. I was using reprepro to maintain partial mirrors, but it required using the output from "dpkg --get-selections" from almost every machine that I needed to mirror packages for. The reprepro program is excellent for making partial mirrors, but it has a drawback in that it doesn't help resolve dependencies. This means that you can't just make a short list of packages and easily build a partial mirror that contains those packages and their dependencies, rather you have to install a machine with those packages and use the list of packages from that machine with reprepro to get a decent mirror. There is another application that will help with the dependencies. It's called germinate, and it will take a short list of packages and a list of repositories and build a bunch of different lists of packages and their dependencies. Germinate will also determine build dependencies for those packages and recursively build a list of builddeps and the builddeps' builddeps. I have thought of making an application that would get germinate and reprepro to work together to help build a decent partial mirror that had the correct set of packages, but the process was a bit time consuming. It's been a while since I've worked on this, since my temporary solution to the problem was to buy a larger hard drive. Currently, I have a full mirror that I keep updated, and a repository of locally built packages next to it. I'm not really happy with this solution, as it uses too much disk space and I'm downloading packages that will never be used, but it's given me time to tackle more important problems. Before writing any code, I would recommend taking a look at both reprepro and germinate, as each of these applications is good at solving half of the problems you describe. I think that an ideal solution would be to write a frontend program that takes a list of packages and upstream repositories, feeds them into germinate, obtains the result from germinate, parse those results and build a reprepro configuration from that, then get reprepro to fetch the appropriate packages. I would be happy to help with this, as I could use such an application, and I already have a meager bit of python code that parses the output of germinate (germinate uses a wiki-type markup in it's output files). I stopped working on the code since I bought a new hard drive, since I just used the extra space to solve the problem for me, but I can bring it back to life, as I would desire to use a more correct solution. -- Thanks: Joseph Rawson signature.asc Description: This is a digitally signed message part.
Re: Statistics for licenses?
Hello, On Thu, 2009-06-04 at 09:10 +0200, Frank Lin PIAT wrote: > > I am looking for some statistics of the [main] licenses used in Debian > packages (or some statistics about the license used in open-source > software at large). > > Are you aware of such analyze? FWIW, I have found those statistics: http://blackducksoftware.com/oss I don't really trust those statistics (ok, I never trust statistics anyway;) because: - CC-** and GFDL aren't listed at all, so documentation isn't included. - All BSD variants are aggregated (improperly analyzed) - Freeware / Public domain aren't listed - Python isn't listed, etc. Creative commons has some statistics about their own licenses: http://wiki.creativecommons.org/License_statistics Freshmeat used to provide some statistics (click on a date): http://web.archive.org/web/*/http://freshmeat.net/stats/ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#532532: ITP: libacme-progressbar-perl -- Perl module providing a s simple progress bar
Package: wnpp Severity: wishlist Owner: Salvatore Bonaccorso * Package name: libacme-progressbar-perl Version : 1.125 Upstream Author : Ricardo SIGNES * URL : http://search.cpan.org/dist/Acme-ProgressBar/ * License : Artistic | GPL-1+ Programming Lang: Perl Description : Perl module providing a simple progress bar Acme::ProgressBar provides a simple solution designed to provide accurate countdowns. No progress bar object needs to be created, and all the calculation of progress through total time required is handled by the module itself. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Xen - Source?
Michael Shuler wrote: > On 06/09/2009 11:49 AM, Andreas wrote: >> Installing it (make), it downloads the binary of the hypervisor! >> "Cloning http://xenbits.xensource.com/linux-2.6.18-xen.hg " # >> (downloading) > > This is an incorrect understanding of that download step - it is a > *source* download from the upstream mercurial repository: > Are you saying the source package does not actually contain the source code, but is just a framework for downloading the actual source? If so, this seems unusual to me. AIUI it's normal practice for a source package to contain a local copy of the source tree because Debian cannot make the assumption that xenbits.xensource.com will always be there. > > You can also download tarballs from the parent web site, if you wish. > So why are these not used in the creation of the source package? Cheers, David. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#532513: ITP: libextutils-pkgconfig-perl -- Perl interface to the pkg-config utility
Package: wnpp Severity: wishlist Owner: Jonathan Yu * Package name: libextutils-pkgconfig-perl Version : 1.12 Upstream Author : Torsten Schönfeld * URL : CPAN * License : Perl (GPL/Artistic) Programming Lang: Perl Description : Perl interface to the pkg-config utility -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Xen - Source?
On 06/09/2009 11:49 AM, Andreas wrote: > Installing it (make), it downloads the binary of the hypervisor! > "Cloning http://xenbits.xensource.com/linux-2.6.18-xen.hg " # > (downloading) This is an incorrect understanding of that download step - it is a *source* download from the upstream mercurial repository: mshu...@aineko:~/src/repos/hg$ hg clone http://xenbits.xensource.com/linux-2.6.18-xen.hg destination directory: linux-2.6.18-xen.hg requesting all changes adding changesets adding manifests adding file changes added 899 changesets with 23501 changes to 20928 files updating working directory 20905 files updated, 0 files merged, 0 files removed, 0 files unresolved mshu...@aineko:~/src/repos/hg$ > So where do I find the source of the xen-Hypervisor? Right where you found it ;) You can also download tarballs from the parent web site, if you wish. -- Kind Regards, Michael -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
apt-get wrapper for maintaining Partial Mirrors
Hi all, We all know that there are various distro's that build around Debian. I had an idea in mind whereby the task of making mirrors for personal distributions can be automated. This can be stated as: if a person wants to keep a customised set of packages for usage with the distribution, the tool should be able to develop dependencies, fetch packages, generate appropriate documentation and then create the corresponding directory structure in the target mirror! The task can be extended to include packages which are currently not under one of the standard mirrors! I think the tool can have immense utility in helping people automate the task of mantaining the repositories. Suggestions, positive and negative are invited. I have not included the impl details as I would first like to evaluate the idea at a feasibility and utility level. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Xen - Source?
Hallo everybody! Xen is distributed with Debian (main) Seems the source-package doesn't contain the code of the hypervisor. Also /lib/modules/2.6-686/kernel/arch/xen/i386/mm/hypervisor.c is not included. Installing it (make), it downloads the binary of the hypervisor! "Cloning http://xenbits.xensource.com/linux-2.6.18-xen.hg " # (downloading) So where do I find the source of the xen-Hypervisor (running below the linux-kernel)? - Or: why could it be distributed with Debian? thanks a lot, Andrew -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: DEP 5 and directory/file names with spaces
On Tue, Jun 09, 2009 at 10:12:48AM -0400, Jonathan Yu wrote: > In my defense, you don't mention how many filenames have newlines (my > estimate is zero.) Because my position was that the frequency of each of these characters is negligible, so the escaping mechanism we choose has no practical impact. Trying to check for newlines in the output of 'tar' would have taken more work and doesn't matter to my point - I agree that newlines are going to be less frequent, but that doesn't invalidate a claim that the others are infrequent enough. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Hint library name (was Re: Naming convention for Java gluelib ?)
On Mon, Jun 8, 2009 at 9:15 PM, Matthew Johnson wrote: > On Mon Jun 08 18:12, Mathieu Malaterre wrote: >> Hi there, >> >> I could find the naming convention for C# binding: >> >> http://pkg-mono.alioth.debian.org/cli-policy/ch-packaging.html#s-gac-naming-versioning >> >> I am now looking for a similar page for a library that would be >> wrapped in Java. What would be the convention for a foo.jar requiring >> a gluelib lib.so ? > > Hi, this is one of the things I'd like to review at debconf this year > since I think this whole area needs reviewing. > http://www.debian.org/doc/packaging-manuals/java-policy/ exists, which > says: > > "If a Java library relies on native code, the dynamic libraries > containing this compiled native code should be installed into the > directory /usr/lib/jni. These dynamic libraries should be shipped in > a separate architecture-specific package named libXXX[version]-jni. > The package containing the Java bytecode (generally > libXXX[version]-java) should depend on this package." > > which doesn't say much about file naming. A quick sample of the archive > shows at least: > > libfoo-java.so, libjfoo.so, libfoojni-fullversion.so > > so, at the moment there's not really a standard. I've CC'd debian-java > in case anyone there isn't reading debian-devel. Excellent ! Quick question, in C# it is possible to hint the wrapped layer what is the gluelib name. Does such mechanism exist in Java ? For instance my jar file is called 'gdcm.jar' and the gluelib is (now): 'libgdcmjni.so' Thanks, -- Mathieu -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#532488: ITP: geanyprj -- an alternative project manager for Geany
Package: wnpp Severity: wishlist Owner: Chow Loong Jin * Package name: geanyprj Version : 0.5-1 Upstream Author : Yura Siamashka * URL : http://plugins.geany.org/geanyprj/ * License : GPL-2+ Programming Lang: C Description : an alternative project manager for Geany GeanyPrj is a plugin for Geany that provides an alternative method for managing projects in Geany, which moves away from Geany's default project management style, which is session-based, instead implementing a system which automatically opens a project when oen of its files are opened. Geany is a small and lightweight integrated development environment using the GTK2 toolkit. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: DEP 5 and directory/file names with spaces
On Wed, Jun 10, 2009 at 12:08:22AM +0900, Charles Plessy wrote: > * List of space-separated pathnames indicating files that have the same > licence and share copyright holders. Question marks indicate any character > and asterisks indicate any string of characters. +1 -- Noah Slater, http://tumbolia.org/nslater -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#532481: ITP: radsecproxy -- RADIUS protocol proxy supporting RadSec
Package: wnpp Severity: wishlist Owner: Faidon Liambotis Package name: radsecproxy Version : 1.3 Upstream Author : Stig Venaas URL : http://software.uninett.no/radsecproxy/ License : Dual BSD/GPL (without OpenSSL exception) Programming Lang: C Description : RADIUS protocol proxy supporting RadSec A generic RADIUS proxy that in addition to usual RADIUS UDP transport also supports TLS (RadSec). It aims to be flexible while at the same time small in size and memory footprint, efficient and easy to configure. . It can be useful as a proxy on site boundaries or in other complex RADIUS routing topologies. It supports both IPv4 and IPv6. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: DEP 5 and directory/file names with spaces
Le Mon, Jun 08, 2009 at 10:15:26AM -0400, Jonathan Yu a écrit : > You know, this is probably a stupid question, but what's wrong with > separating file patterns with newlines, as continuations? Hi Jonathan, first of all, do not worry that your proposition was ignored, but it is sometimes more interesting to wait for multiple propositions to come instead of answering immediately. In this discussion, I will try to limit myself to one message per day (and maybe per thread, I do not know). Also, I am subscribed to -devel in digest mode, to help myself to refrain answering too fast. It is important to leave time to more subscribers of this list to contribute. For the readability of the file, as well as its diffs as you noted, using newlines seems to perform quite well. I think that the biggest drawback is that it is not compliant with RFC-822, which will then necessitate contorsions like in debian/control, to define wihch field is foldable, which is not, which has a special first line,… For the moment, this is not be the only field with this issue: the License field has a special first line, and its newlines are kept after parsing. But maybe it is better to not accumulate exceptions. Note that if we use spaces as separators and claim that the field is 822-compliant, then it is still possible to use newlines as a separator, despite it will still require to escape or quote the spaces in the paths and file names, if it ever happens to be necessary. Let's try to sum up. Currently the DEP contains: * **`Files`** * Required. However, the first **`Files`** field can be omitted and its value will be assumed to be '*'. * List of space-separated globbing pathnames (see `man 7 glob` for more details) indicating files that have the same licence and share copyright holders. * If multiple `Files` declaratioun match the same file, then only the last match counts. My personal wiew about the specification is that it will be best if we keep it short. After all, the old version on the wiki attracted much criticism because it was getting too big. For this reason, I decided to refer directly to glob(7) when I rewrote it as DEP5, so that it would not be necessary to define what the * and ? wildcards are doing. But I like the expectation that the field contents should be pastable to shell commands (like xargs if there are newlines), and glob(7) seems to specify things that are not supported by simple commands such as ls, for instance [:space:] to denote a space. Would everybody agree if the description of the field content would be changed to the following, assuming that it could be made clear somewhere else in the specification that fields are 822-compliant unless stated otherwise: * List of space-separated pathnames indicating files that have the same licence and share copyright holders. Question marks indicate any character and asterisks indicate any string of characters. As wrote earlier, for the cornercases, if for instance a package would contain two directories named 'user manual' and 'user?manual' with a different license, it is probably better to talk upstream anyway, and there is still the possibility of solving the problem at the level of the upstream archive. Discussion of these cornercases could be part of a FAQ if necessary, but my feeling is to not enter into such consideration in the specification itself. Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: DEP 5 and directory/file names with spaces
Manoj Srivastava wrote:
On Tue, Jun 09 2009, Lars Wirzenius wrote:
Some highlights:
* two carriage return chars (\r)
* one escape char
* 5431 spaces
* 1 double quotes (")
* 98 single quotes (')
* 64 asterisks (*)
* 524 commas
* 3 backslashes
* 51601 percent chars (%)
No newlines, eh? Seems like the one glob per line wins.
Also no tabs, so we can keep horizontal and vertical split of pathnames.
But what glob rule?
One simple:
- * as shell glob
- \\ (3 cases)
- \* (64 cases)
but how to specify \r (2 cases), \e (one case) and the non-7 bit ASCII (793
cases)?
(surely some sequences are non UTF-8 compatible, e.g. 3 0xFE)
ciao
cate
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: DEP 5 and directory/file names with spaces
In my defense, you don't mention how many filenames have newlines (my estimate is zero.) But IANADD so do what you want :-) On Tue, Jun 9, 2009 at 3:47 AM, Steve Langasek wrote: > On Mon, Jun 08, 2009 at 09:11:09PM -0700, Steve Langasek wrote: >> vor...@gluck> cd /srv/lintian.debian.org/laboratory/source >> vor...@gluck> find . -name '*,*' | wc -l >> 9 >> vor...@gluck> find . -name '* *' | wc -l >> 23 >> vor...@gluck> > > Sorry, this is an incorrect test; on closer examination, the upstream > tarballs aren't unpacked in the lintian lab. The actual count (from a > recursive tar ztvf) is > > commas: 1032 > spaces: 7305 > total files: 4180690 > > By number of affected packages, this is: > > commas: 57 > spaces: 310 > >> This is bikeshedding in the extreme. > > But I think this still stands. > > -- > Steve Langasek Give me a lever long enough and a Free OS > Debian Developer to set it on, and I can move the world. > Ubuntu Developer http://www.debian.org/ > slanga...@ubuntu.com vor...@debian.org > > > -- > To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > > -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#532430: ITP: udunits -- Library for the programatic handling of units of physical quantities
Alastair McKinstry debian.org> writes: > * Package name: udunits > Version : 2.1.7 > Upstream Author : UCAR > * URL : http://www.unidata.ucar.edu/software/udunits/ > * License : BSD Yes please! I needed that once or twice for R packages that build on top of it, and created local deb packages. I never pushed these further because I disliked UCAR's "you have go to click and register here before downloading" pages. Oh, and I see I even blogged about it: http://dirk.eddelbuettel.com/blog/2004/09/04#udunits Nice to see this in Debian, at last! Cheers, Dirk -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: DEP 5 and directory/file names with spaces
On Tue, Jun 09 2009, Lars Wirzenius wrote:
> Some highlights:
>
> * two carriage return chars (\r)
> * one escape char
> * 5431 spaces
> * 1 double quotes (")
> * 98 single quotes (')
> * 64 asterisks (*)
> * 524 commas
> * 3 backslashes
> * 51601 percent chars (%)
No newlines, eh? Seems like the one glob per line wins.
manoj
--
Computers can figure out all kinds of problems, except the things in the
world that just don't add up.
Manoj Srivastava
Bug#532439: ITP: polylib -- The Polyhedral Library (PolyLib for short) operates on objects
Package: wnpp Severity: wishlist Owner: "serge guelton " * Package name: polylib Version : 7 Upstream Author : Vincent Loechner * URL : http://icps.u-strasbg.fr/polylib * License : LGPL Programming Lang: C Description : the polyhedral library The Polyhedral Library (PolyLib for short) operates on objects made up of unions of polyhedra of any dimension. It was first developed by Doran Wilde at IRISA, in Rennes, France, in connection with the ALPHA project. -- System Information: Debian Release: 5.0.1 APT prefers stable APT policy: (700, 'stable'), (650, 'testing'), (550, 'unstable') Architecture: i386 (i686) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Sie sind einmalig und Ihre Meinung ebenfalls!
Guten Tag, die heutige Welt ist in ständiger Bewegung! Als Verbraucher können Sie sich Gehör verschaffen und zur Konzeption von neuen Produkten und Dienstleistungen beitragen. Deshalb möchten wir Ihnen anbieten, unserem Verbraucherpanel beizutreten. So bekommen Sie die Möglichkeit, punktuell an Umfragen über vielseitige Themen teilzunehmen, deren Häufigkeit Sie selbst bestimmen. Ihre Teilnahme an den Umfragen wird belohnt. Sie erhalten für jede beantwortete Umfrage eine Vergütung. Ihr Betrag variiert je nach Dauer des Fragebogens. Sie verwalten Ihr Online-Bezahlsystem selbst. Die Anmeldung ist ganz einfach und dauert nur zwei Minuten. Es genügt, auf den folgenden Link zu klicken: http://de.panel.opinea.com/?utm_source=5sent&utm_medium=email&utm_campaign=5sent Falls dieser Link nicht aktiviert ist, müssen Sie ihn in Ihren Browser kopieren und einfügen. Ansonsten können Sie auf unserer Website http://de.panel.opinea.com die Rubrik "ANMELDUNG" anklicken. Wir garantieren Ihnen absolute Vertraulichkeit. Ihre Antworten werden grundsätzlich als statistische Werte benutzt und Ihre persönlichen Angaben niemals an Dritte weitergegeben. Ihnen bleibt freigestellt, ob Sie auf die zugeschickten Fragebogen antworten möchten oder nicht. Falls Sie uns einen Kommentar oder eine Beanstandung über die vorliegende Anfrage zusenden möchten, schicken Sie bitte eine Nachricht auf unsere Internetseite de.pa...@opinea.com Das Opinea-Panel-Team http://panel.opinea.com ---
Bug#532430: ITP: udunits -- Library for the programatic handling of units of physical quantities
Package: wnpp Severity: wishlist Owner: Alastair McKinstry * Package name: udunits Version : 2.1.7 Upstream Author : UCAR * URL : http://www.unidata.ucar.edu/software/udunits/ * License : BSD Programming Lang: DaCDaC(C, C++, C#, Perl, Python, etc.) Description : Library for the programatic handling of units of physical quantities The UDUNITS package supports units of physical quantities (e.g., meters, seconds). Specifically, it supports conversion between string and binary representations of units, arithmetic manipulation of units, and conversion of numeric values between compatible units. The package is written in the C programming language. -- System Information: Debian Release: 5.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: powerpc (ppc) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: DEP 5 and directory/file names with spaces
ti, 2009-06-09 kello 00:47 -0700, Steve Langasek kirjoitti:
> Sorry, this is an incorrect test; on closer examination, the upstream
> tarballs aren't unpacked in the lintian lab. The actual count (from a
> recursive tar ztvf) is
>
> commas: 1032
> spaces: 7305
> total files:4180690
>
> By number of affected packages, this is:
>
> commas: 57
> spaces: 310
For further amusement (I want my shed painted pink, with polkadots in
lime-green), attached please find a) a script to compute frequencies of
bytes in filenaems in all lenny main source packages b) the output of
the script.
I unpacked the source packages using the unpack-debian-sources script in
http://code.liw.fi/extrautils/bzr/trunk/ (bzr branch); I apologize for
not having made a release that includes the script yet.
Some highlights:
* two carriage return chars (\r)
* one escape char
* 5431 spaces
* 1 double quotes (")
* 98 single quotes (')
* 64 asterisks (*)
* 524 commas
* 3 backslashes
* 51601 percent chars (%)
> > This is bikeshedding in the extreme.
>
> But I think this still stands.
I changed my mind. I want black with skulls and crossbones in silver,
plus bunnies in gold.
#!/usr/bin/python
import os
import sys
counts = {}
for top in sys.argv[1:]:
for dirname, dirnames, basenames in os.walk(top):
for x in basenames:
for c in x:
counts[c] = counts.get(c, 0) + 1
for c in sorted(counts.keys()):
print "%3d %s %d" % (ord(c), repr(c), counts[c])
13 '\r' 2
27 '\x1b' 1
32 ' ' 5431
33 '!' 81
34 '"' 1
35 '#' 342
36 '$' 1049
37 '%' 51601
38 '&' 166
39 "'" 98
40 '(' 348
41 ')' 330
42 '*' 64
43 '+' 7143
44 ',' 524
45 '-' 834270
46 '.' 3237353
48 '0' 535175
49 '1' 516998
50 '2' 478215
51 '3' 229333
52 '4' 317429
53 '5' 163675
54 '6' 214617
55 '7' 124864
56 '8' 156637
57 '9' 87415
58 ':' 883
59 ';' 9
60 '<' 57
61 '=' 597
62 '>' 66
63 '?' 27
64 '@' 1748
65 'A' 164851
66 'B' 79193
67 'C' 201391
68 'D' 156687
69 'E' 204747
70 'F' 91842
71 'G' 78624
72 'H' 55258
73 'I' 149702
74 'J' 18033
75 'K' 32199
76 'L' 131432
77 'M' 280240
78 'N' 99264
79 'O' 90816
80 'P' 141881
81 'Q' 16678
82 'R' 159067
83 'S' 230612
84 'T' 176242
85 'U' 57109
86 'V' 36488
87 'W' 38912
88 'X' 32973
89 'Y' 16593
90 'Z' 5389
91 '[' 111
92 '\\' 3
93 ']' 110
94 '^' 157
95 '_' 1178360
96 '`' 81
97 'a' 2554343
98 'b' 671246
99 'c' 2171257
100 'd' 1236447
101 'e' 3577704
102 'f' 875451
103 'g' 1287462
104 'h' 1269265
105 'i' 2388345
106 'j' 183252
107 'k' 579332
108 'l' 2151027
109 'm' 1606322
110 'n' 2218732
111 'o' 2109188
112 'p' 2131207
113 'q' 103211
114 'r' 2040057
115 's' 2334579
116 't' 2933157
117 'u' 880994
118 'v' 484188
119 'w' 315390
120 'x' 663838
121 'y' 444930
122 'z' 116657
123 '{' 1
124 '|' 2
125 '}' 1
126 '~' 2272
128 '\x80' 23
129 '\x81' 5
130 '\x82' 6
131 '\x83' 10
132 '\x84' 26
133 '\x85' 2
134 '\x86' 7
136 '\x88' 4
138 '\x8a' 7
139 '\x8b' 12
140 '\x8c' 17
141 '\x8d' 1
143 '\x8f' 4
144 '\x90' 2
145 '\x91' 3
147 '\x93' 5
148 '\x94' 20
149 '\x95' 11
150 '\x96' 1
151 '\x97' 6
152 '\x98' 4
153 '\x99' 8
154 '\x9a' 3
155 '\x9b' 1
156 '\x9c' 22
157 '\x9d' 18
158 '\x9e' 2
159 '\x9f' 5
160 '\xa0' 20
161 '\xa1' 9
162 '\xa2' 1
163 '\xa3' 1
164 '\xa4' 15
165 '\xa5' 4
166 '\xa6' 1
167 '\xa7' 9
168 '\xa8' 16
169 '\xa9' 11
170 '\xaa' 3
171 '\xab' 1
172 '\xac' 11
173 '\xad' 4
174 '\xae' 3
175 '\xaf' 1
176 '\xb0' 12
177 '\xb1' 2
178 '\xb2' 13
179 '\xb3' 11
180 '\xb4' 24
181 '\xb5' 5
182 '\xb6' 8
183 '\xb7' 5
184 '\xb8' 9
185 '\xb9' 6
186 '\xba' 2
187 '\xbb' 3
188 '\xbc' 12
189 '\xbd' 10
191 '\xbf' 1
195 '\xc3' 44
197 '\xc5' 2
204 '\xcc' 9
212 '\xd4' 3
221 '\xdd' 3
223 '\xdf' 2
226 '\xe2' 17
227 '\xe3' 4
228 '\xe4' 9
229 '\xe5' 1
232 '\xe8' 1
233 '\xe9' 13
234 '\xea' 24
235 '\xeb' 60
236 '\xec' 91
237 '\xed' 22
238 '\xee' 1
239 '\xef' 5
241 '\xf1' 1
244 '\xf4' 3
246 '\xf6' 5
248 '\xf8' 1
252 '\xfc' 1
254 '\xfe' 3
Bug#532415: ITP: liblas -- ASPRS LiDAR data translation toolset
Package: wnpp Severity: wishlist Owner: Debian GIS Project * Package name: liblas Version : 1.2.1 Upstream Author : Howard Butler et al * URL : http://liblas.org/ * License : BSD Programming Lang: C++ Description : ASPRS LiDAR data translation toolset libLAS is a C/C++ library and toolset for reading and writing ASPRS LAS versions 1.0, 1.1 and 1.2 data. The LAS format is a sequential binary format used to store data from sensors and as intermediate processing storage by some LiDAR-related applications. libLAS has C, C++, .NET, and Python APIs. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: DEP 5 and directory/file names with spaces
Peter Samuelson wrote: First, as I've said elsewhere, this thread is just about the most impressive bikeshedding session I've ever seen. In my defence (I started this sub-bikeshedding): it was a sentence in a postscriptum. Technically: on handling external data: for every rules there will be exception. But no, I don't think debian should support filename components with '/'. I think we have enough freedom from policy, for such extreme cases, to repacking sensibly the sources in a new orig.tar.* So IMO I would like to have file description in a shell format, so that: - a paste copy to "ls" command is a good test for maintainer and reader - paste and copy works also to check license and files I really don't think we should support in filename, nor control character (which are also difficult (very ugly) to quote in shell language). But IMHO spaces (common in windows), comma (common for revisions) and "extended" characters should be allowed. Continuing to the slash thread: So I'll try and stick to a single post, and I'm only posting because I don't think I've seen mention of the following problem: [Gunnar Wolf] Yup - But the newline is also a valid (altough, yes, very uncommon) part of a filename. So are non-UTF-8 byte sequences, and I suspect those are a great deal more common in filenames than newlines. If you want your copyright file to be UTF-8, you have to escape those byte sequences somehow. I propose something very simple: ? to escape any single byte that seems problematic in any way. Spaces, tabs, newlines, the ISO-8859-1 registered trademark symbol, etc., etc. I mean, we don't need this transform to be reversible, do we? I think it should be reversible, or we will find a case where two files will be coded into one encoding. E.g. this virtual case: a source (and tarball done in ISO 8859-15) currency/ currency/$ (0x24 in ISO 8859-1, ISO 8859-15) currency/ (0xA3 in ISO 8859-1, ISO 8859-15) currency/ (0xA5 in ISO 8859-1, ISO 8859-15) currency/ (0xA4 in ISO 8859-15) Ehi! but these cases cannot be written easily in shell code (in a UTF-8 environment). Simple problem, not so simple solution. But eventually: - every source package should use be coded with UTF-8 filename components, without control chars nor slashes and backslashes. This could be done automatically, but in few (I hope very seldom) cases. (so the burden is put to maintainer, but very seldom, and not in DEP5/policy and tools) ciao cate -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: DEP 5 and directory/file names with spaces
On Mon, Jun 08, 2009 at 09:11:09PM -0700, Steve Langasek wrote: > vor...@gluck> cd /srv/lintian.debian.org/laboratory/source > vor...@gluck> find . -name '*,*' | wc -l > 9 > vor...@gluck> find . -name '* *' | wc -l > 23 > vor...@gluck> Sorry, this is an incorrect test; on closer examination, the upstream tarballs aren't unpacked in the lintian lab. The actual count (from a recursive tar ztvf) is commas: 1032 spaces: 7305 total files: 4180690 By number of affected packages, this is: commas: 57 spaces: 310 > This is bikeshedding in the extreme. But I think this still stands. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
