* Manoj Srivastava:
Not quite correct. Policy has the job of docmenting what is
technically correct, and selecting one of a number of equally viable
technical options where numerous possibilities exist. The primary
purpose of policy is to ensure that diverse packages under
* Raphael Hertzog:
Edit debian/changelog, and change the : by + and you're probably done.
Shouldn't policy be updated to reflect this?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
* Frank Küster:
Florian Weimer [EMAIL PROTECTED] wrote:
* Raphael Hertzog:
Edit debian/changelog, and change the : by + and you're probably done.
Shouldn't policy be updated to reflect this?
Which part? 5.6.12 already talks about that.
A colon is explicitly allowed if the version
* Kari Pahula:
I can assume that Eiffel Software is arguing that anything compiled
with Eiffel Studio is a derived product and needs to be under GPL too.
It seem like software compiled using Eiffel Studio links to the GPLed
run-time library, so such a claim would make a lot of sense.
The
* Joerg Jaspert:
As *many* rejects out of the NEW-Queue[2] are still due to broken or
incomplete copyright-files - lets refresh that information.
Just for clarification, since there seems to be this increased
interest in copyright notices: Do developers need to verify that these
copyright
* Josselin Mouette:
There is no difference between decoders and encoders. Both require
patent licenses.
But as I understand it, only the encoding patents are enforceable.
I've never seen a compelling argument why this should be the case.
The arguments looked more or less like wishful
* Russell Coker:
This factor makes it significantly different from the other programs
which are afflicted with patent claims. If Thomson has made clear
statements about a common use case of software based on their
patents in Debian then it's quite different to a battle between
Adobe and
* Goswin von Brederlow:
Anything that runs from current amd64.debian.net or its mirrors.
Both debian-amd64 and debian-pure64? Great, thanks.
They are just aliases for the same thing since always.
Oh, this wasn't clear from the FAQ. Fortunately, all this is now OBE.
--
To UNSUBSCRIBE,
* Goswin von Brederlow:
Can you remeber to close this bug when maintainer uploads for amd64
get enabled?
It would also be interesting to know which AMD64 architecture variants
permit seamless upgrades to the official AMD64 version.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
* Goswin von Brederlow:
It would also be interesting to know which AMD64 architecture variants
permit seamless upgrades to the official AMD64 version.
Anything that runs from current amd64.debian.net or its mirrors.
Both debian-amd64 and debian-pure64? Great, thanks.
--
To UNSUBSCRIBE,
* David Weinehall:
Upstream includes non-free manpages these days, so in reality, we have
already forked. Further Debian-specific changes are needed to address
bugs such as #295211 (upstream does not document our libc/kernel
combination).
What manpages in upstream are non-free? Do we have
* Russ Allbery:
Your points about sync(8) and tzselect(8) seem reasonable on the surface,
but the rest of this seems to be disregarding the fact that manpages and
manpages-dev are not native packages. Those man pages are included in
that package because they're maintained together upstream
* Joe Smith:
http://people.debian.org/~forcer/debian-scheme-policy/debian-scheme-policy.html/
Which may be an unofficial policy mandates certain symlinks managed
by alternatives to scheme interpreters based on what they
support. The virtual package names have been accepted by consensus
* Chad Walstrom:
I'm trying to package up tex2page and noticed that there is no virtual
package for scheme-interpreter. I would like to specify in the
Depends: that some sort of scheme-interpreter is required instead of
having to list each of them individually.
Any thoughts on this
[EMAIL PROTECTED]
Changed-By: Florian Weimer [EMAIL PROTECTED]
Description:
libnetpbm10 - Shared libraries for netpbm
libnetpbm10-dev - Development libraries and header files
libnetpbm9 - Shared libraries for netpbm
libnetpbm9-dev - Development libraries and header files
netpbm - Graphics
* Isaac Jones:
I'd like to ask the Debian community to look at Haskell98 and some of
the research extensions[2] and give us some input as to what would
make Haskell more attractive to you.
Uhm, most of the things on Debian's (as opposed to individual
developer's) whishlist are
* Matt Zimmerman:
One of the appealing things about the Python language is their batteries
included philosophy: users can assume that the standard library is
available, documentation and examples are written to the full API, etc.
Would this really be a problem if the minimal Python
* Josselin Mouette:
We are talking about a MP3 *decoding* plugin. Like the ones we
already have in so many packages we have stopped counting.
Just to clarify since you put that emphasis on decoding:
There is no difference between decoders and encoders. Both require
patent licenses. There
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Wed, 25 Jan 2006 14:15:53 +0100
Source: debsecan
Binary: debsecan
Architecture: source all
Version: 0.4.1
Distribution: unstable
Urgency: low
Maintainer: Florian Weimer [EMAIL PROTECTED]
Changed-By: Florian Weimer [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 23 Jan 2006 13:49:46 +0100
Source: smstools
Binary: smstools
Architecture: source i386
Version: 1.16-1.1
Distribution: unstable
Urgency: high
Maintainer: Mark Purcell [EMAIL PROTECTED]
Changed-By: Florian Weimer [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sat, 21 Jan 2006 15:50:32 +0100
Source: xml2rfc
Binary: xml2rfc
Architecture: source all
Version: 1.30.dfsg-1
Distribution: unstable
Urgency: low
Maintainer: Florian Weimer [EMAIL PROTECTED]
Changed-By: Florian Weimer [EMAIL
* Thomas Viehmann:
I think that not shipping unmaintained and unsupported packages is a
benefit. Packages need a maintainer to enter, I think they should need
one to stay.
A real problem is that willingness to maintain a package in unstable
is not as good a predictor as you might think for
* Matt Zimmerman:
It is important, in particular, to account for the fact that Ubuntu is not
the only Debian derivative, and that proposals like yours would amount to
Debian derivatives being obliged to fork *every source package in Debian*
for the sake of changing a few lines of text.
Such
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 17 Jan 2006 14:34:37 +0100
Source: cook
Binary: cook cook-doc cook-rsh
Architecture: source i386 all
Version: 2.26-1
Distribution: unstable
Urgency: low
Maintainer: Florian Weimer [EMAIL PROTECTED]
Changed-By: Florian Weimer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 17 Jan 2006 19:21:52 +0100
Source: debsecan
Binary: debsecan
Architecture: source all
Version: 0.4.0
Distribution: unstable
Urgency: low
Maintainer: Florian Weimer [EMAIL PROTECTED]
Changed-By: Florian Weimer [EMAIL PROTECTED
* Raphael Hertzog:
I believe Ubuntu fills an important gap in the Debian world and as such
I'm not satisfied when Ubuntu is diverging too much from Debian, and the
only way to avoid divergence is to merge back what's useful and to provide
better solution for derivatives when there's a need
* Anthony Towns:
If you'd like to make suggestions about ideas that would be useful,
What about: stop threatening your fellow developers?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
* Alejandro Bonilla:
I want to learn how to debug and see what went wrong. How can I
learn to debug this kind of things or how can I enable some
debugging for this kind of things?
valgrind is quite helpful for debugging such problems related to
memory-management. You could also have a look
* Russ Allbery:
Debian isn't perfect at this. There are portions of the Debian
infrastructure where the exact version that Debian is running are not
necessarily available. However, these are generally considered within the
project to be anomolies and Debian *does* have a general committment
* Bernd Eckenfels:
Paul TBBle Hampson [EMAIL PROTECTED] wrote:
Maybe the one-true-stable-key idea is the way to go after all...
One key by distribution?
If this means one key per suite (sarge, etch, ...), and no yearly key
rollover, I agree. 8-)
--
To UNSUBSCRIBE, email to [EMAIL
* Michael Vogt:
Sorry for the delay. I'm preparing a new upload that adds the 2006
archive key to the default keyring.
Please try to get a new self-signature without an expiration data
first.
If they key is compromised, it has to be (manually) revoked anyway.
Rotating it once per year
* Bernd Eckenfels:
IOW using the old key to sign the new key only requires that the old
key be good at one point during the new year, whereas continuing to
use the old key requires that it be good all year.
Yes, but it breaks a long term usage like web of trust.
The Debian archive key does
* Steve Langasek:
For a user with a compromised local network, the only safe solution is to
validate the new key via some web of trust.
No, the web of trust doesn't solve the problem. I'm pretty sure most
DDs don't even know who is authorized to issue a new archive key. A
user has no way to
* Steve Langasek:
I would encourage you to log into merkel and verify, directly and
securely, the key at /org/ftp.debian.org/web/ziyi_key_2006.asc; sign it; and
upload your signature to the public keyservers as well, if you are satisfied
that this is the key that is being used on
* Ryan Murray:
On Tue, Dec 27, 2005 at 03:45:26PM +1100, Anand Kumria wrote:
There seems to be a problem, localised to spohr, with the sending of
emails. I've uploaded some packages recently and have neither received
The problem is on your end -- mail to these MXs is being 451'd, and
your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Wed, 28 Dec 2005 09:52:53 +0100
Source: debsecan
Binary: debsecan
Architecture: source all
Version: 0.3.3
Distribution: unstable
Urgency: low
Maintainer: Florian Weimer [EMAIL PROTECTED]
Changed-By: Florian Weimer [EMAIL PROTECTED
* Anand Kumria:
Please take a look at see what is happening for the domains:
progsoc.uts.edu.au and progsoc.org
Might yet another instance of master's mail problems. See the thread
on -devel, and the one on exim-users (Potential logic error in retry
handling for IPv4+IPv6 hosts).
Short
* Michelle Konzack:
Am 2005-12-22 16:04:45, schrieb Florian Weimer:
With traffic included? How's that more than 10$ per gigabyte
transferred and month? 8-)
IF you can reach 34 Mbit!
My old colo E3 at UUnet in Kehl/Germany was 5000 Euro/month
plus traffic
* Michelle Konzack:
Because we do not get 34 MBit and we have not a netload
of 100% 24/7 the price per GByte is around 50 US$/GByte.
This means you still have plenty capacity you've already paid for,
supporting Steinar's claim that bandwidth is cheap.
Just think about it. 8-)
--
To
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 27 Dec 2005 14:23:03 +0100
Source: debsecan
Binary: debsecan
Architecture: source all
Version: 0.3.2
Distribution: unstable
Urgency: low
Maintainer: Florian Weimer [EMAIL PROTECTED]
Changed-By: Florian Weimer [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sun, 25 Dec 2005 18:12:25 +0100
Source: debsecan
Binary: debsecan
Architecture: source all
Version: 0.3.1
Distribution: unstable
Urgency: low
Maintainer: Florian Weimer [EMAIL PROTECTED]
Changed-By: Florian Weimer [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Fri, 23 Dec 2005 15:35:46 +0100
Source: debsecan
Binary: debsecan
Architecture: source all
Version: 0.3
Distribution: unstable
Urgency: low
Maintainer: Florian Weimer [EMAIL PROTECTED]
Changed-By: Florian Weimer [EMAIL PROTECTED
* Michelle Konzack:
Am 2005-12-19 09:56:27, schrieb Olaf van der Spek:
Are you paying 10 $/gb?
Where is it that expensive?
I pay 450.000 DHs (around 57.000 US$) in Morocco
for an E3 (34 MBit) with traffic included.
With traffic included? How's that more than 10$ per gigabyte
transferred
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 22 Dec 2005 10:27:54 +0100
Source: debsecan
Binary: debsecan
Architecture: source all
Version: 0.2.2
Distribution: unstable
Urgency: low
Maintainer: Florian Weimer [EMAIL PROTECTED]
Changed-By: Florian Weimer [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 20 Dec 2005 11:17:28 +0100
Source: debsecan
Binary: debsecan
Architecture: source all
Version: 0.2.1
Distribution: unstable
Urgency: low
Maintainer: Florian Weimer [EMAIL PROTECTED]
Changed-By: Florian Weimer [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 19 Dec 2005 19:26:06 +0100
Source: debsecan
Binary: debsecan
Architecture: source all
Version: 0.2
Distribution: unstable
Urgency: low
Maintainer: Florian Weimer [EMAIL PROTECTED]
Changed-By: Florian Weimer [EMAIL PROTECTED
* Steinar H. Gunderson:
My comments are about the same as on IRC:
- Disk space is cheap, bandwidth is cheap.
Depends. Decent IP service costs a few EUR per gigabyte in most parts
of the world.
Thus, anything sacrificing lots of human power and CPU power to save on disk
or bandwidth just
* Andreas Metzler:
Afaict from the webpage 7zip (LZMA) is quite a bit slower bzip2. -
Have you perhaps run some benchmarks?
Memory use during decompression would be interesting, too.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Wed, 14 Dec 2005 16:09:20 +0100
Source: debsecan
Binary: debsecan
Architecture: source all
Version: 0.1
Distribution: unstable
Urgency: low
Maintainer: Florian Weimer [EMAIL PROTECTED]
Changed-By: Florian Weimer [EMAIL PROTECTED
* Goswin von Brederlow:
Mirror size per arch (in MiB):
| sarge | etch | sid | all
-+---+--+---+---
source | 9339 | 9419 | 11495 | 30252
This looks suspicious. I expected that the total number would be
significantly less than the sum of the suites
* Lionel Elie Mamane:
On Thu, Dec 08, 2005 at 09:30:52PM +0100, Wouter Verhelst wrote:
The fact that my primary MX is only available through IPv6, and that
this is the case for other people who're having problems too might
then be a better chance at being the problem.
My primary MX is
* Lionel Elie Mamane:
You also have one IPv4-only MX,
No, I don't.
But Exim 4 thinks so:
[EMAIL PROTECTED]
router = dnslookup, transport = remote_smtp
host capsaicin.mamane.lu [2001:888:19f0::2] MX=9
host capsaicin.mamane.lu [2001:888:19f0:2::2] MX=9
* Marc Haber:
May I ask why you pollute the general development mailing list for
that?
The comment in the code is:
/*
* This is a temporary (probably) hack to fix a bug on tru64 5.1
* and 5.1a. Sometimes, pthread_cond_timedwait() doesn't actually
* return
* A. Mennucc:
in both cases, the first part of the install was OK, but, after
reboot, when APT was called to upgrade the system, it stopped
claiming:
E: This installation run will require temporarily removing the essential
package e2fsprogs due to a Conflicts/Pre-Depends loop. This is
On Thu, Nov 24, 2005 at 06:45:58PM +, Ian Jackson wrote:
So the best idea is indeed for
downstream systems to have policies which are no more strict than
upstream systems.
Would it be possible for master to make call-outs to chiark ?
would that solve the problem ?
I don't think so.
What tool do you think is the easiest to perform this task?
In the Debian context, most developers who maintain individual patches
use dpatch. quilt is a similar tool. There's also Chris Mason's mq
extension for Mercurial, and Stacked GIT, but these haven't been
packaged for Debian yet.
--
* Henning Makholm:
Scripsit Florian Weimer [EMAIL PROTECTED]
* Jochen Voss:
I found the example at http://www.cits.rub.de/MD5Collisions/ quite
impressive. They have two different valid PostScript files with
identical MD5 sums. I don't know how much computing time they used,
though
I was really asking for a GUI tool that allows me to update the current
patches, one by one, to the current upstream sources, going through
each patch chunk and letting me update the chunk if it doesn't apply
correctly.
Ah, something like an interactive three-way merge? ediff, kdiff3 and
* Anthony Towns:
On Sat, Nov 26, 2005 at 10:59:57AM +0100, Florian Weimer wrote:
For the exploits we have seen so far to work, the malicious party
needs upload access to the archive and has to plant a specially
crafted package there, for which they have created an evil twin
package. (Same
* Jochen Voss:
On Tue, Nov 29, 2005 at 02:08:45PM +0100, Goswin von Brederlow wrote:
According to slashdot articles you can generate human readable files
(like the Packages file) with md5sum collision in ~45minutes on a
modern cpu now.
I found the example at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 29 Nov 2005 15:05:46 +0100
Source: libalgorithm-diff-perl
Binary: libalgorithm-diff-perl
Architecture: source all
Version: 1.19.01-2
Distribution: unstable
Urgency: low
Maintainer: Florian Weimer [EMAIL PROTECTED]
Changed
* Stephen Gran:
No noticable time difference between the two, either. So, I don't
think this is the real problem.
You could be right.
The problem is still present, unfortunately. One more data point: A
couple of seconds before the last bounce was generated, murphy (which
is on the same
* Anthony Towns:
On Fri, Nov 25, 2005 at 07:59:40PM +0100, Florian Weimer wrote:
* Anthony Towns:
(I'm amazed the security crisis we're having is about deb sigs
*again*, when we're still relying on md5sum which has a public exploit
available now...)
These exploits are irrelevant as far
* Thiemo Seufer:
A: Why do you lock your car up[1]?
B: Because it looks like having it locked is better then not having it
locked.
A: Sorry, but that's a snake oil rationale. Anybody can pick the lock
and break in. Anybody can smash a window and break in. etc.
Wrong, it makes break-ins
* Henning Makholm:
Scripsit Peter Samuelson [EMAIL PROTECTED]
You may laugh if you wish, but I think it's annoying to have to move to
a hash function whose hexadecimal representation takes 64 bytes, which
doesn't leave much room on an 80-column line to describe what the hash
is hashing.
From time to time, master seems to bounce mail routed to mail.enyo.de
with the following error message:
[EMAIL PROTECTED]
retry time not reached for any host after a long failure period
Is anybody experiencing a similar problem?
I tried to debug it myself, using the information I could
* Steinar H. Gunderson:
On Sat, Nov 26, 2005 at 10:59:57AM +0100, Florian Weimer wrote:
So? If SHA256 is so much better, why is that nobody can prove it, or
at least can provide some evidence which supports that claim? The
numbers are bigger is the main argument at this point, which
* Henning Makholm:
I wouldn't use real base64, though, because it would mean that you can
use its hashed output as a file name.
Good point. One might replace / with _ and omit the final =.
Having a + in the hash should be safe in most contexts.
It should be replaced with -. Beyond
* Stephen Gran:
Once you know the retry rules, try
/usr/sbin/exinext [EMAIL PROTECTED]
That will tell you what's recorded in the retry database currently.
exinext ist not SUID, and I haven't got sufficient permission on
master to access the retry database:
[pid 29063]
* Jeroen van Wolffelaar:
I tried to debug it myself, using the information I could access on
master, but I couldn't gather enough evidence to present to the
postmasters so far.
But other DD's can also only do a limited amount of research, the only
way to really find out is asking a
* Stephen Gran:
It probably makes sense to disable IPv6 support in Exim on master,
independently of my current problem. I'm going to suggest this to
postmaster@ once I figured out a good way to implement this.
I doubt that's the problem. This is from my logs:
2005-08-10 13:33:46
* Adeodato Simó:
* Florian Weimer [Thu, 24 Nov 2005 18:28:04 +0100]:
Hi,
AFAIK, binary NMus aren't announced on debian-devel-changes.
Binary-only uploads are announced in the appropriate
debian-devel-$ARCH-changes list.
According to
http://murphy.debian.org/lists/debian-devel-i386
* Anthony Towns:
(I'm amazed the security crisis we're having is about deb sigs
*again*, when we're still relying on md5sum which has a public exploit
available now...)
These exploits are irrelevant as far as the Debian archive is
concerned. (And that's not because hardly any sarge user
* Anthony Towns:
Personally, I think it's cryptographic snake oil, at least in so far
as it relates to Debian. I remain interested in seeing any realistic
demonstration of how a Debian user could reasonably rely on them for
any practical assurance.
The assurance doesn't come from the
* Marc Brockschmidt:
Today (or last night, whatever), the dak installation on ftp-master was
changed to not accept packages that include more than 3 parts, which are
usually the binary version and the compressed control and data
tarballs. This means that signed binary packages are rejected.
* Andreas Schuldei:
i have not given up that hope yet and i invest a considerable
amount of time working on this issue as part of my work on the
DPL-Team. others there do so, too.
Is this the delegation to teams item on
http://wiki.debian.org/DPLTeamCurrentIssues? A rather cryptic
reference,
* Christian Perrier:
Is there something I can do for getting my address unlisted (apart
from again reducing the load I put on b.d.o...which I did again down
to the lowest acceptable refresh rate on my side)?
There is a BTS mirror on merkel. Maybe you could mirror the bug
reports you are
* Steinar H. Gunderson:
-frepo is an optimization switch, designed to avoid multiple instantiations
of the same template (reducing its size). You should be able to compile just
fine without it, but your binaries will be bigger.
Thanks to the .gnu.linkonce sections, the finaly binary should be
* Jérôme Marant:
Is it currently possible to upload amd64 packages to ftp-master?
amd64 is not yet part of the archive. It depends on the so-called
mirror split.
* Jérôme Marant:
Quoting Florian Weimer [EMAIL PROTECTED]:
* Jérôme Marant:
Is it currently possible to upload amd64 packages to ftp-master?
amd64 is not yet part of the archive. It depends on the so-called
mirror split.
I guess so, but I haven't seen any status update about
* Andy Teijelo Pérez:
El Martes, 8 de Noviembre de 2005 1:11, Thomas Bushnell BSG escribió:
Erast Benson [EMAIL PROTECTED] writes:
I understand your concern. We will release ISO image with CDDL/GPL
sources very soon. Majority of them already available at /apt. The rest
is comming.
Once
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 8 Nov 2005 15:53:09 +0100
Source: libwant-perl
Binary: libwant-perl
Architecture: source i386
Version: 0.09-1
Distribution: unstable
Urgency: low
Maintainer: Florian Weimer [EMAIL PROTECTED]
Changed-By: Florian Weimer [EMAIL
* Kurt Roeckx:
Companies *do* make them, though. They are *tiny*, low-power
*cheap*. The 386SX is perfect for the embedded market.
Intel still sells 386 DX, SX and others:
http://www.intel.com/design/intarch/intel386/index.htm
Still doesn't warrant supporting them, though. 8-)
--
To
* Bastian Venthur:
We know what steps it takes ot resupport i386. What kind of work would
be needed to rename i386 to x86 or ia32?
I think we should at least consider to rename,
Oh, come on, it's just a name which is mostly used by Debian's
infrastructure, and not by end users. Changing it
* Henning Makholm:
Scripsit Florian Weimer [EMAIL PROTECTED]
The GPL does fail the Dissident test because it does not permit
anonymous changes.
Your copy of the GPL must have been garbled in transmission.
Please fetch a fresh copy from a trusted source.
What is a trusted source? The copy
* Wouter Verhelst:
Lets assume you have GPL-ed project dpkg. Any change to foo.c must be
contributed back to the community.
No, that's not true.
Any *distributed* changes to foo.c must be contributed back to the
community.
Huh? Why do you think so?
--
To UNSUBSCRIBE, email to [EMAIL
* Frank Küster:
Because that's what the GPL says, in relatively plain language.
I cannot find it there. Moreover, if it was in there, the GPL would
fail the Dissident test and the Dessert Island test.
The GPL does fail the Dissident test because it does not permit
anonymous changes.
* Nick Jacobs:
You mean, it's seriously been proposed that a
significant amount of work should be done to restore
support for a processor that has not been manufactured
for 10 years?
I think AMD still makes them.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe.
* Alex Ross:
2) 2,300 Debian packages available for immediate usage.
How do you solve the problem that you cannot legally distribute
software which is licensed under the GNU General Public License and is
linked against a libc which is covered by the CDDL? Have you ported
GNU libc?
3)
* Luca Capello:
I'm in the process of debianize some CL software [1] and I've the same
problem as bug #328423: some extra features of the package needs other
packages to be installed, so I don't know if the package should use
Suggests or Recommends.
Use Recommends: if the functionality added
* Peter Van Eynde:
So is there anything else I can do?
Bootstrap with one of the other supported Lisp implementations?
MLton recently solved a similarly problem by manually building the
supported architectures outside the buildd network.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
* Bill Gatliff:
From this:
http://www.gnu.org/philosophy/license-list.html
Common Development and Distribution License (CDDL)
http://www.opensolaris.org/os/licensing/cddllicense.txt
This is a free software license which is not a strong copyleft; it
has some complex restrictions
* Erast Benson:
Are you seriously saying that whatever Sun does must be ok, so we can
do the same?
i'm not claiming anything.
But are you seriosly saying that SUN violates GPL?
In the past, Sun shipped the GNU components on separate media. (I
don't know if you had to order them
* Jochen Voss:
Hello,
On Sat, Oct 29, 2005 at 07:04:02PM +0200, Frank Küster wrote:
There were also some bugs for tetex-* that were never sent to the
Maintainer: field, namely the debian-tetex-maint mailing list.
Here is another one. The following message (related to bug #335689)
spend
=low
+
+ * Non-maintainer upload
+ * Map type of Index and Translation-* files to text/plain.
+
+ -- Florian Weimer [EMAIL PROTECTED] Sun, 30 Oct 2005 11:04:48 +0100
+
apt-proxy (1.9.32) unstable; urgency=low
[ Chris Halls ]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
* Michael Vogt:
When fully supported by the archive, the diff support will be
completely transparent, no changes on your side necessary.
When downloading the Index file, APT does not send instructions to
bypass the proxy cache:
T 212.9.189.177:51459 - 212.9.189.169: [AP]
GET
* Miles Bader:
Florian Weimer [EMAIL PROTECTED] writes:
There are people in this world who can read and program PostScript.
Sure, and it's the preferred form of modifcation for removing
ink-wasting background images from Powerpoint presentations, but: This
is not the kind of modifcation
* Bernhard R. Link:
* Florian Weimer [EMAIL PROTECTED] [051025 13:51]:
* Steve Langasek:
Frank Lichtenheld has already posted an announcement[4] detailing the
release team's plans for the question of non-DFSG documentation in main.
Just to clarify, is technical documentation
* Frank Küster:
Konstantinos Margaritis [EMAIL PROTECTED] wrote:
I just received this and thought this guy might use some more
feedback...
You may answer I have a girl/boy friend if in fact it is a
wife/husband. I have not yet understood whether he knows the difference
between Linux
* Jason Clinton:
http://www.vnunet.com/vnunet/news/2144710/sun-kicks-oem-programme-jds
This is about the Java Desktop System. AFAIK, this is just a GNOME
variant, and not an implementation of the Java language.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe.
501 - 600 of 844 matches
Mail list logo
