UTF-8 man pages

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I'm trying to package a simple tool that wants a Japanese string in its man page. It would appear that currently, man pages use fixed encodings that vary depending on which locale's man page is being looked up; English uses ISO-8859-1, so it's

Re: UTF-8 man pages

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Roger Leigh wrote: [...] I would personally like to see this happen, but until it does we are limited (I believe) to the glyphs described in groff_char(7). I am not aware of any Japanese support at all except in specially-patched versions. I do

Re: Package cache

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Eduard Bloch wrote: [...] If you want to keep the files aside but ie. compressed than you should use a compressing filesystem. But if you want something working on access, expect it to perform very bad. Ie. if you want to install the files from

Zero Install (was: Package cache)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: [...] looks pretty cool, but someone should talk to them about this: The effect of this is that distribution-provided packages are often more reliable than upstream ones (since upstream don't get to hear about many of

Re: DFSG violations: non-free but no contrib

with a maliciously programmed GSM stack would turn into a rather efficient cellphone jammer.) -- David Given [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: DFSG violations: non-free but no contrib

in GSM protocol stacks... what *is* the Debian project's policy on using Debian with safety-critical systems, anyway? There are a number of licenses that specifically prohibit the use of their software in such environments; do these count as DSFG-free? Is there any such software in Debian? -- David

Re: Leverage in licensing discussions

embedded operating systems and/or proprietary third-party libraries... -- David Given [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Leverage in licensing discussions

Tzafrir Cohen wrote: [...] Up until 1968 the same reasoning wasused to present people from connecting anything but phones provided by Bell to the Bell telephone network. You were not even allowed to connect a modem through an accustic coupler. If I recall correctly, back in the old days, it

Re: Hosting the Debian/kCygwin port?

semantics, etc. While installation is still a bit tortuous, they have a buildd and claim to support a decent number of packages... Is this of interest to anyone? - -- David Given d...@cowlark.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http

Re: Why no Opera?

it looks horribly complicated. -- David Given [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Debian's Linux kernel continues to regress on freedom

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Joerg Jaspert wrote: [...] Those that pass NEW for whatever reason are reviewed. Yes, I did reject lots of such packages for copyright-file brokenness. :) Speaking as someone who has just had a package pass NEW, I would like to thank you for

Re: How to start porting to a new ARCHITECTURE?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michelle Konzack wrote: [...] since 2007-08-01 I am now jobless (yeah, the new French GOV do not like that I stay in the army as PMC) and today (Saturday) I was asked by an owner of a german Enterprise whether it is possibel to port GNU/Linux,

Re: Proposal regarding future packaging

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 John H. Robinson, IV wrote: [...] I like this idea, especially if there were a short description about each program and relevent configuration files. I like this too. Finding what a package has just installed is one of the biggest holes in Debian

Re: Proposal regarding future packaging

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 John Goerzen wrote: [...] Too crude? That's a simple command, easily found in a relevant manpage. In true Unix fashion, its output can be easily piped to other commands. What's crude about it? Well, it doesn't actually tell me what I need to

Re: Idea of Debian mascot

Lars Wirzenius wrote: [...] I'd really rather see something nicer than an ant as a mascot. :) How about a cockroach? Beautifully engineered, indestructable, and they're *everywhere*... -- David Given [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject

Re: triggers wishlist

Michael Biebl wrote: [...] Add update-initramfs to that list. It can take quite some time to regenerate the initramfs. Packages that update the initramfs are e.g. udev, cryptsetup or uswsusp, splashy/usplash *raises hand* Before it blew up, my old NSLU2 (a 266MHz ARM with 32MB RAM) used to

Re: What should postrm purge actually do?

Andreas Bombe wrote: [...] The user may have imported the configuration from some other machine, or intend to use the configuration elsewhere. The usefulness of user configuration is therefore not tied to the installed state of the package on this system. Particularly since the user may have

Re: DEP5: proposed versioned url for Format: does not work

Jonas Smedegaard wrote: [...] I would recommend in the meantime to use a versioned URL of your choosing. As I believe is documented - the specific URL should be only an example. FWIW, I have recently tried to put together a DEP5 compliant copyright file for a package I'm working on. I say

Re: Change default PATH for Jessie / wheezy+1

Thomas Goirand wrote: [...] Exactly what do you need from sbin as a user? I use stuff from sbin as user all the time. A quick glance at /sbin shows these commands that I use on a regular basis: blkid fdisk all the fscks all the mkfss hdparm ifconfig (before this discussion I'd never even

Re: O: ted -- lightweight .DOC editor

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Neil Williams wrote: [...] The problems described in #501638 would mean that the package would not be allowed back into Debian unless fixed. It looks like this isn't an issue any more --- the relevant paragraph from the docs is now: Ted is

Re: O: ted -- lightweight .DOC editor

Konstantin Khomoutov wrote: [...] There's still no such thing as the GNU Public License, what the author seemingly try to refer to is called GNU General Public License, that is, the 'G' in GPL stands for General, not for GNU. IRL that's actually a link to the FSF page, so it seems clear to me

Re: nacl and CPU frequency.

On 22/09/12 15:28, peter green wrote: [...] In order to build successfully nacl needs to determine the CPU frequency (the CPU frequency determined at build time is not used in the final binaries afaict but if it's not determined then the build will fail as it will consider the implementation

Re: Really not about udev, or init sytsems

On 25/11/12 19:02, John Paul Adrian Glaubitz wrote: [...] I've been a vivid Amiga user since 1991* and I still love these machines and I am supporting the efforts to get Debian back onto m68k. Yet, I do not think this should happen at all costs. There haven't been no new 68k processors for

Re: ColdFire / m68k

John Paul Adrian Glaubitz wrote: [...] How much are these instruction set compatible with the classical m68k processors? Would we be able to have an m68k port of Debian which runs both on the original m68k CPUs and the ColdFire series? AFAIK the ColdFire is nearly, but not quite, a strict

Accepted ufiformat 0.9.8-1 (source i386)

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Format: 1.8 Date: Wed, 03 Dec 2010 18:48:09 + Source: ufiformat Binary: ufiformat Architecture: source i386 Version: 0.9.8-1 Distribution: unstable Urgency: low Maintainer: David Given d...@cowlark.com Changed-By: David Given d...@cowlark.com

Accepted wordgrinder 0.2-1 (source i386)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 19 Jan 2008 10:13:06 + Source: wordgrinder Binary: wordgrinder Architecture: source i386 Version: 0.2-1 Distribution: unstable Urgency: low Maintainer: David Given [EMAIL PROTECTED] Changed-By: David Given [EMAIL PROTECTED

Accepted wordgrinder 0.2-2 (source i386)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 04 Feb 2008 20:45:50 + Source: wordgrinder Binary: wordgrinder Architecture: source i386 Version: 0.2-2 Distribution: unstable Urgency: low Maintainer: David Given [EMAIL PROTECTED] Changed-By: David Given [EMAIL PROTECTED

Accepted ufiformat 0.9.4-2 (source i386)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 21 Mar 2008 22:18:00 + Source: ufiformat Binary: ufiformat Architecture: source i386 Version: 0.9.4-2 Distribution: unstable Urgency: low Maintainer: David Given [EMAIL PROTECTED] Changed-By: David Given [EMAIL PROTECTED

Accepted ufiformat 0.9.3-3 (source i386)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 18 Aug 2007 21:54:15 +0100 Source: ufiformat Binary: ufiformat Architecture: source i386 Version: 0.9.3-3 Distribution: unstable Urgency: low Maintainer: David Given [EMAIL PROTECTED] Changed-By: David Given [EMAIL PROTECTED

Accepted wordgrinder 0.3.1-1 (source i386)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 15 Sep 2008 23:14:39 +0100 Source: wordgrinder Binary: wordgrinder Architecture: source i386 Version: 0.3.1-1 Distribution: unstable Urgency: low Maintainer: David Given [EMAIL PROTECTED] Changed-By: David Given [EMAIL PROTECTED

Accepted wordgrinder 0.3.2-1 (source i386)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 19 Feb 2009 23:54:29 + Source: wordgrinder Binary: wordgrinder Architecture: source i386 Version: 0.3.2-1 Distribution: unstable Urgency: low Maintainer: David Given d...@cowlark.com Changed-By: David Given d...@cowlark.com

Accepted wordgrinder 0.3.3-1 (source i386)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 14 Dec 2009 21:42:12 + Source: wordgrinder Binary: wordgrinder Architecture: source i386 Version: 0.3.3-1 Distribution: unstable Urgency: low Maintainer: David Given d...@cowlark.com Changed-By: David Given d...@cowlark.com

Accepted wordgrinder 0.5.1-1 (source amd64)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 13 Dec 2013 01:23:54 + Source: wordgrinder Binary: wordgrinder Architecture: source amd64 Version: 0.5.1-1 Distribution: unstable Urgency: low Maintainer: David Given d...@cowlark.com Changed-By: David Given d

Accepted wordgrinder 0.4.1-1 (source amd64)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 14 Apr 2013 21:12:31 + Source: wordgrinder Binary: wordgrinder Architecture: source amd64 Version: 0.4.1-1 Distribution: unstable Urgency: low Maintainer: David Given d...@cowlark.com Changed-By: David Given d...@cowlark.com

Accepted ufiformat 0.9.9-1 (source amd64)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 15 Oct 2013 19:35:37 +0900 Source: ufiformat Binary: ufiformat Architecture: source amd64 Version: 0.9.9-1 Distribution: unstable Urgency: low Maintainer: David Given d...@cowlark.com Changed-By: David Given d...@cowlark.com

Accepted wordgrinder 0.6-2 (source all amd64) into unstable

Given <d...@cowlark.com> Changed-By: David Given <d...@cowlark.com> Description: wordgrinder - simple word processor for writing first drafts wordgrinder-doc - simple word processor for writing first drafts (documentation) wordgrinder-ncurses - simple word processor for writing

Accepted wordgrinder 0.6-3 (source all amd64) into unstable

Given <d...@cowlark.com> Changed-By: David Given <d...@cowlark.com> Description: wordgrinder - simple word processor for writing first drafts wordgrinder-doc - simple word processor for writing first drafts (documentation) wordgrinder-ncurses - simple word processor for writing

Accepted wordgrinder 0.6-1 (source all amd64) into unstable, unstable

Given <d...@cowlark.com> Changed-By: David Given <d...@cowlark.com> Description: wordgrinder - simple word processor for writing first drafts wordgrinder-doc - simple word processor for writing first drafts (documentation) wordgrinder-ncurses - simple word processor for writing

Accepted wordgrinder 0.6-4 (source all amd64) into unstable

Given <d...@cowlark.com> Changed-By: David Given <d...@cowlark.com> Description: wordgrinder - simple word processor for writing first drafts wordgrinder-doc - simple word processor for writing first drafts (documentation) wordgrinder-ncurses - simple word processor for writing

Accepted wordgrinder 0.7.1-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 2 Nov 2017 18:53:00 + Source: wordgrinder Binary: wordgrinder wordgrinder-ncurses wordgrinder-x11 wordgrinder-doc Architecture: source Version: 0.7.1-1 Distribution: unstable Urgency: medium Maintainer: David Given &l

Accepted wordgrinder 0.7.2-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 29 Nov 2018 21:18:05 +0100 Source: wordgrinder Binary: wordgrinder wordgrinder-ncurses wordgrinder-x11 wordgrinder-doc Architecture: source Version: 0.7.2-1 Distribution: unstable Urgency: medium Maintainer: David Given

How to handle packages which build themselves with bazel?

I'm looking into converting some of my upstream packages to use Google's bazel build system, because it makes life much easier as a developer. Unfortunately, with my other hat on, it makes life much harder as a package maintainer: bazel is very keen on downloading source packages and then

Re: How to handle packages which build themselves with bazel?

gt; I'm not following the updates for bazel packaging, but you > may browse the packaging work of the corresponding team > to see whether there is anything you are interested in: > https://salsa.debian.org/bazel-team/bazel > > On Wed, 2022-06-08 at 17:18 +0200, David Given wrote: