* 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
* 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
* 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
* 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,
* 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.
* 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
* 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:
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
* 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 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
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
* 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.
* 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
* 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
* 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
* 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
* 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
* 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
* 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
* 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
* 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
* 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
* 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
* 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]
* 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
* 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
* 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
* 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
* 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
* 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
* 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
* 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
* 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
* 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,
* 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,
* 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
in some
environments.
--
Florian Weimer[EMAIL PROTECTED]
University of Stuttgart http://cert.uni-stuttgart.de/
RUS-CERT +49-711-685-5973/fax +49-711-685-5898
Graham Wilson [EMAIL PROTECTED] writes:
see apt-listchanges, which is a great tool for looking at changelogs
before you install packages.
Hardly everybody has got a full Debian mirror in the same rack. ;-)
--
Florian Weimer[EMAIL PROTECTED]
University of Stuttgart
Hans Reiser [EMAIL PROTECTED] writes:
You'll note that ReiserFS anticipated the GNU GPL V3 by including
clauses that forbid removal of credits in its license, and for a long
time I have been telling Stallman that he needs to get V3 of the GPL
out the door.
Oh, I think it's natural to assume
Hans Reiser [EMAIL PROTECTED] writes:
I want the same visibility of credits for reiserfs that movies give
for their actors.
So you are concerned with the missing ad when mkreiserfs runs?
In this case, your analogy is wrong. The message does not give proper
credit to developers (actors), but
Matt Zimmerman [EMAIL PROTECTED] writes:
I urge anyone who participates in package maintenance to read this section
in the Developer's Reference:
http://www.debian.org/doc/developers-reference/ch-pkgs.en.html#s-bug-security
For political reasons, I'd rather like to file bug reports using the
Petter Reinholdtsen [EMAIL PROTECTED] writes:
There seem to be someone believing that standard documents should be
treated as software. Standards are not software. Standards do not
improve if everyone is allowed to modify them and publish the modified
version as an updated version of the
Marco d'Itri [EMAIL PROTECTED] writes:
I fully agree. Banning RFCs from debian is just silly.
And I wonder what's next? fsf-funding(7)? The GPL?
Debian really needs a separate policy for works which are not
software.
Branden Robinson [EMAIL PROTECTED] writes:
So be it. The Social Contract and the traditions of our project
compel us to make principled decisions, not politically expedient
ones.
Not correct. Look at the handling of security issues. The project
has chosen (never formally, though) that it
Andrew Suffield [EMAIL PROTECTED] writes:
Debian really needs a separate policy for works which are not
software.
We could have a policy for non-software, but it should still exclude
non-free things. What you are trying to say is Debian really needs to
include non-free things.
There are
Josip Rodin [EMAIL PROTECTED] writes:
On Fri, Jul 04, 2003 at 12:39:46PM +0200, Florian Weimer wrote:
So be it. The Social Contract and the traditions of our project
compel us to make principled decisions, not politically expedient
ones.
Not correct. Look at the handling of security
Branden Robinson [EMAIL PROTECTED] writes:
There are borderline cases, such as the GFDL or free works in
non-editable formats (PS, PDF, in some cases even HTML), or licenses
or other documents of perceived legal relevance.
I have argued on debian-legal that licenses as applied to specific
Tollef Fog Heen [EMAIL PROTECTED] writes:
| If libd1 is uploaded and only one of proga and libv0 is recompiled with
| libd1 this results in proga linked with both so-versions of the library.
| I remember problems with two so-versions of libpng, later with
| libssl0.9.6 and libssl0.9.7, and
* Thiemo Seufer:
How could clamav possibly have a stable engine and suddenly start to
need libfoo?
Most antivirus software today is a framework for mobile code
distribution. Too often, you have to replace MIME decoders, HTTP
decoders, and the like.
I find it rather strange that new
* Jose Carlos Garcia Sogo:
Here is some kind of explanation:
http://www.tribulaciones.org/blog/computers/ext3-performance_27-09-2004.html
The most common performance issue with ext3 file systems is caused by
software that accesses files in the order returned by readdir. Has
this been ruled
* Steinar H. Gunderson:
On Wed, Oct 06, 2004 at 03:12:33PM +0200, Florian Weimer wrote:
The most common performance issue with ext3 file systems is caused by
software that accesses files in the order returned by readdir. Has
this been ruled out?
What other, sane alternatives
* Loïc Minier:
The best option would be for RPC services to ue a port pool, not
overlapping standard ports, but this might be impossible.
I think the best option would be to allow the system administrator to
statically allocate the ports used by RPC programs. This would help
packet filters,
* Josip Rodin:
On Thu, Oct 07, 2004 at 11:09:23PM +0200, Andreas Barth wrote:
the developers reference was much updated in the last time.
[...]
If there are any issues or suggestions, please don't hesitate to speak
to me.
For example, why clutter debian-devel-announce with things like
Package: wnpp
Severity: wishlist
* Package name: libperlio-eol-perl
Version : 0.05
Upstream Author : Autrijus Tang [EMAIL PROTECTED]
* URL : CPAN
* License : GPL/Artistic
Description : PerlIO layer for normalizing line endings
This layer normalizes any
Package: wnpp
Severity: wishlist
* Package name: libio-digest-perl
Version : 0.10
Upstream Author : Chia-liang Kao ()
* URL : CPAN
* License : GPL/Artistic
Description : Calculate digests while reading or writing
This module allows you to calculate
Package: wnpp
Severity: wishlist
* Package name: libfile-type-perl
Version : 0.22
Upstream Author : Paul Mison [EMAIL PROTECTED]
* URL : CPAN
* License : GPL/Artistic
Description : determine file type using magic numbers
File::Type uses magic numbers
* Andreas Barth:
- volatile is not just another place for backports, but should only
contain changes to stable programs that are necessary to keep them
functional;
Can volatile receive critical updates which are usually not applied to
stable because backports are not available for some
* Loïc Minier:
Florian Weimer [EMAIL PROTECTED] - Thu, Oct 07, 2004:
I think the best option would be to allow the system administrator to
statically allocate the ports used by RPC programs. This would help
packet filters, too.
While I see the benefit of your suggestion, for packet
* Nathanael Nerode:
Unless of course the firmware itself is GPL'd, and therefore no one
can legally give it out without offering the source as well.
It is GPLed. This is why it hasn't been put in non-free. :-P
Until they do one of these two things, the firmware is not safe to
distribute.
* Andreas Barth:
Can volatile receive critical updates which are usually not applied to
stable because backports are not available for some reason?
Are you speaking about mozilla? ;)
Mozilla, GnuPG, and maybe even PHP 4, depending on sarge's lifetime.
Other complex packages can easily enter
* Hilko Bengen:
Florian Weimer [EMAIL PROTECTED] writes:
File::Type uses magic numbers (typically at the start of a file) to
determine the MIME type of that file.
File::Type can use either a filename, or file contents, to determine the
type of a file.
(Another svk dependency.)
Does
* NOKUBI Takatsugu:
At Mon, 11 Oct 2004 12:47:25 +0200,
Hilko Bengen wrote:
Does its feature differ from File::MMagic (libfile-mmagic-perl)?
It seems under different license. File::MMagic is The Apache License
The code is under a BSD-style license with a documentation requirement
which
* Thomas Bushnell:
John Hasler [EMAIL PROTECTED] writes:
The intent implied by publically releasing a work under the GPL is well
understood and widely known. I don't believe that they would stand any
chance of getting an injunction, let alone damages.
You cannot infer person A's intent in
* Martin Schulze:
Unfortunately this changed the kernel architecture from s390 to
s390x.
May I suggest to fix this in the kernel?
* Glenn Maynard:
Perhaps I should make my program 'par' command-line compatible!
OTOH, when you have so many small files it is not convenient.
I don't really understand the use of allowing thousands of tiny parts.
What's the intended end use?
I suppose it could be used for multicast file
* Andreas Barth:
There are no autobuilders for testing-security.
So what's missing at this stage? Machines? An active local system
administrator? Or someone who is trusted enough to integrate the
buildds into the security build infrastructure?
If it's machines or the local system
* Cord Beermann:
I added a temporary(?) fix, and bounced the latest report to the list.
Thanks, but it ended up in the archive (under the URL
http://lists.debian.org/debian-devel-announce/2004/10/msg00010.html),
but not in the inboxes of subscribers.
* Luke Kenneth Casson Leighton:
i'm forwarding this to debian devel for people's attention because
it would appear that debian has lost a quite large opportunity - [...]
I'm surprised SourceForge didn't switch to AIX. Really.
(They didn't upgrade to Mailman 2.1, by the way. *sigh*)
* Ben Pfaff:
Sorry, I don't maintain non-free packages.
In this case, please file an ITO bug for gnu-standards.
* Hamish Moffatt:
FairUCE is a spam filter that prevents spam from reaching the
recipient's inbox by verifying the identity of the sender. It will stop
By what mechanism?
According to the AlphaWorks article, it's mostly a challenge-response
system which suppresses the CR mechanism if some
* Gürkan Sengün:
* Package name: lapispuzzle.app
Version : 0.9.1
Upstream Author : Banlu Kemiyatorn [EMAIL PROTECTED]
* URL : http://home.gna.org/garma/lapispuzzle/index.html
* License : GNU GPL
Description : almost a clone of Street Puzzle Fighter
* Bruce Perens:
The Linux Core Consortium would like to have Debian's involvement. This
organization has revived what I originally proposed to do as the LSB -
to make a binary base for Linux distributions that could be among
several distributions who would share in the effort of
* Michael Banck:
2. GNOME succeeded for the desktop.
Are there any proprietary COTS applications for GNOME where vendor
support isn't bound to specific GNU/Linux distributions?
Maybe GNOME is a good example of cross-vendor cooperation (but so is
GCC), but would be quite surprised if this
* Brian Nelson:
Anyone, developer or non-developer, can help fix toolchain problems.
However, the only people who can work on the testing-security
autobuilders are ... the security team and the ftp-masters?
It's about infrastructure, so the security team is out (they are just
users of this
* Steve Langasek:
Um, what's the concrete use case for a cross-distro standard network
configuration interface?
VPN software, intrusion detection systems, software for CALEA support,
centralized management software.
1 - 100 of 844 matches
Mail list logo
