No. It is not up to the Debian maintainer to decide that some
contributor has written enough of the code to also be mentioned in the
(C) lines in a particular file. But as soon as upstream lists them
either in a file header or the AUTHORS file the Debian maintainer has to
copy that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sat, 21 Mar 2009 19:46:17 +0100
Source: xbindkeys-config
Binary: xbindkeys-config
Architecture: source amd64
Version: 0.1.3-2
Distribution: unstable
Urgency: low
Maintainer: Joerg Jaspert jo...@debian.org
Changed-By: Joerg Jaspert jo
On 11693 March 1977, Dominik Smatana wrote:
Or should I edit these files and add missing licenses (copy paste
from main file)?
Talk to upstream. Unless you have written the files it is *NOT* yours to
declare them being licensed in whatever way.
--
bye, Joerg
vorlon hmm, I should fill in the
On 11690 March 1977, Norbert Preining wrote:
Can please move
texlive-doc-el
from the section lisp to the section doc, it is definitely not a lisp
file but only documentations in Greek.
Haha. Yeah well. Seems i missed that.
Furthermore, you have moved
cm-*
to fonts. Maybe
On 11690 March 1977, Timo Jyrinki wrote:
There are also at least aspell-el and openoffice.org-l10n-el, which
are certainly not Lisp unless Greek has a lot of parentheses :)
It seems the priority of the -el match was a little above what it should
have been. :)
Well, there is a reason we do
On 11690 March 1977, Raphael Geissert wrote:
php Everything about PHP
Does everything really means everything?
At least the following are missing:
php5-adodb
libphp-adodb
libmarkdown-php
I haven't looked at others.
It should. PHP was a late addition, so we might have
As the current RM Master ;) I see two realistic possibilities:
1) Someone just write me a mail if I should some part of the cruft
report or ping me on IRC. This would of course scale to a few cases
only.
Inacceptable. The latest cruft report was done by me for example. Having
someone mail
Maybe it could be interesting to open an accessibility section?
Maybe, maybe not. What packages would you put into it?
--
bye, Joerg
Getty LOL die Telefonnummer vom Arbeitsamt Mönchengladbach ist echt 404-0?
Getty Soll das nen schlechter Scherz sein?
--
To UNSUBSCRIBE, email to
ruby Everything about ruby, an interpreted object
oriented
language.
java Everything about Java
How about a cli section about everything related to Mono and the
Common Language Infrastructure (aka .NET) ? That makes quite a
We plan on changing the current sections in the archive. With the rapid
growth of archive, many of them have become too big to be useful anymore.
According to my knowledge of dak, the sections are global. Which means
that we don't have to worry about a possible kernel update for
lenny+1/2.
On 11674 March 1977, Edward Betts wrote:
webfeed - RSS/Atom feed readers, aggregator and utilities
Not enough packages, can stay in web, especially as that gets rid of httpds.
--
bye, Joerg
ftpbot cron.daily time, unlocking: slave_NEW
mhy ftpbot: oh bugger off, slave_NEW isn't affected by
Have sense to inaugurate a section with all the R modules? Nowadays
many of them are in math.
$ apt-cache search r- | grep ^r- | wc - l
133
Thats ok, get me a good name and short description for it please.
r is not a good name, i think.
--
bye, Joerg
* wiggy just looking at
video
mplayer*
That is already in.
vswitch*
No hit for this match?!
--
bye, Joerg
GyrosGeier I've annoyed Ganneff enough with that package already, no
reason to top it off by a build-depend on emacs for writing control
files
pgpLuKXMhKlrs.pgp
Description: PGP signature
You also want totem* and kaffeine*.
Done.
*-dbg packages could go in their own section(s) (debug, or libdebug
appdebug?); otherwise, I think that they should remain with (the bulk of) the
packages for which they provide debug data.
All debug packages will go in the debug section.
--
Get me a short description for it.
Compiler, libraries, and tools for OCaml: a static typed ML language
implementation supporting functional, imperative, and object-oriented
programming styles.
You have an interesting definition of short, i stopped after : for
now. :)
(Its a different thing
On 11674 March 1977, Aaron M. Ucko wrote:
As I mentioned directly to override-change before encountering this
message, I'd argue that my goo package is a (somewhat exotic)
candidate. In general, here's a first cut at a full list, including
it and your initial proposals:
Thanks.
--
bye,
Like the other poster, cli is very confusing. If we have enough
packages (get me a list/matches :) ), im not against a section for it,
but cli wouldnt be my favorite name for it.
I’m not sure for the section name, but here is a list of matches:
Select one of cli-mono or ecma-cli and please
Hello world,
As Lenny is finally released, and we are early in the cycle for squeeze,
now is the best time to do some long-needed changes to our archive.
Much of what we are currently doing is not visible to you as a user of
this archive, but the action we talk about now is:
We plan on changing
Not like it is *that* important, but we now have more than 100
OCaml-related source packages in the archive, most of which are
libraries for OCaml development.
I don't if that warrants an ocaml section, which is your call, but
if it does, well, ... heads up :-)
Get me a short description
On 11673 March 1977, Adeodato Simó wrote:
* Joerg Jaspert [Thu, 26 Feb 2009 21:07:35 +0100]:
database
libmysql*
libdb4*
I'm not sure these (and possibly *some* of the other lib* packages
included in the listing) should be moved out of Section: libs. I can see
On 11673 March 1977, Frans Pop wrote:
localisationsLanguage packs
I'd prefer localization.
- We use en_US in general - ize
Well, I dont really care. Fine, adjusted.
- Having the section name plural seems inconsistent with other
sections.
Dito.
video
[...]
database Databases
[...]
database
postgresql*
pg*
sqlite*
mysql*
libmysql*
db4.*
libdb4*
firebird*
sql-*
lisp Everything about Lisp
Is this just about Common Lisp, or other Lisp dialects as well? I'm
mainly referring to Scheme here, as it is another Lisp dialect in
(relatively) widespread use (the third one being Emacs-Lisp).
Its lisp. Not one special part of it, just lisp.
I have already packaged this. I was going to submit an ITP and upload
it through a sponsor in the next days.
This is one reason why an ITP is expected *before* beginning work.
Yea, indeed. I completely forgot about it, sorry.
How did you package it? If it includes the git source do not
That way one could tell, even when offline, if a package hasn't been
updated in ten years.
I hope we don't have any of those.
And those that we have, we can also spot them by old Standards-Version
in lintian warnings.
If anyone can suggest me a decent heuristics to spot a 'rotting'
Also, I'd suggest (if we get it), we also use it for things like
videos of talks about Debian, that kind of things.
No.
--
bye, Joerg
lenny schneidet nie chilis und wascht euch dann _nicht_ die hände und reibt
euch dann an der nase.
lenny uargs, wie das brennt
lenny hammer. das ist ja
I am not a dak hacker, nor an ftpteam or wanna-build guy. That being
said, it looks like a lot of the information you store and the functions
for comparison look an awful lot like the stuff dak currently has. Does
it make sense to consolidate, and expand dak to handle the extra things
you
On 11631 March 1977, Anthony Towns wrote:
There seem to be some issues with the ftp mirror on merkel:
$ pwd
/srv/ftp.debian.org/ftp
$ ls -l dists/sid/Contents-powerpc.diff/ | tail -n2
-rw-rw-r-- 1 archvsync archvsync 2053 Jan 14 13:40 Index
?- ? ? ? ?
Umh... This might be the cause, then. Our mirror sync has died three
days in a row - At 16:37, 15:49 and 17:36 (GMT-6):
From where are you pulling?
--
bye, Joerg
Five exclamation marks, the sure sign of an insane mind.
-- Terry Pratchett, Reaper Man
--
To
Umh... This might be the cause, then. Our mirror sync has died three
days in a row - At 16:37, 15:49 and 17:36 (GMT-6):
From where are you pulling?
syncproxy.wna.debian.org
Completly different machine, so not the cause for your trouble.
--
bye, Joerg
Linus: Wenn Darl McBride die Macht
I think that the name of FTP team or ftpmasters which we often use
is slightly misleading to people we are not aware of each and every
bit of how the project works.
And there are many people who contribute to Debian more occasionnaly
than those core folks who know everything about our
IMO, it would make sense to merge Debian sections into a debtags facet
so that you can have multiple sections when it makes sense. The facet
could still be controlled by ftpmasters if that was desired. And aptitude
could use that facet to keep a logical tree but a package could then
appear
On 11623 March 1977, Jörg Sommer wrote:
I'm a Debian Maintainer and would like to use the upload of packages via
scp. Is this service available for Debian Maintainers? Where do I have to
place my public ssh‐key?
As this needs a login to a Debian machine, no.
--
bye, Joerg
Free Beer is such
I don't remember using sections in over 4 years of Debian usage, though
I had already used GNU/Linux for a few months before I switched to
Debian. But I doubt even a user new to GNU/Linux would use them much.
Everyone that uses a tool like aptitude does use them much. I guess
similar is true
I will be importing planeta's subscribers list into /es soon and
re-direct URL and feeds, because that's how the people wanted it,
their way or highway.
It would be nice if you wait until we can set up some not strict but needed
rules about the content we want in planet/es.
Well, I *hope*
Since planet.d.o now supports multiple languages, what about closing the
old planet*.debian.net services?
http://planeta.debian.net/
http://planet-fr.debian.net/
http://planet.debian.net/
Those initiatives were useful because they proved that they were needed,
but multiplying the
We add them to planet.debian.org when they request it. The Spanish
people did so, the french not. It would be good if they do, to keep it
sane in one place, but thats not our call.
Please note that by Spanish people you mostly mean a few developers
who, paraphrasing Joss, were in pain due to
What is the correct usage of this section?
Is it for packages that is related to the desktop itself or is it for
packages that links against kdelibs ?
Should a game using kdelibs go to section:games or section:kde?
games.
should a web browser using kdelibs go to section:web or
I guess we actually need to consider what the sections are good for.
Asking in a random irc channel at least didn't reveal any real answers.
So what about killing the concept of sections entirely ?
Sure, if at some point a replacement is suitable and *well integrated*
into those Debian tools
Hey,
if you are a DM uploading your packages, please pay extra attention in
the next few days. We just changed the underlying code in our archive
software to be less awkward. While we did test that (using the help from
Eugene V. Lyubimkin (thanks)) there might be cases not covered by our
tests.
Hi
after some discussion within the ftpteam we just modified a few override
entries (15 to be exact). The following packages moved from standard to
optional:
strace
sharutils
policycoreutils
tcsh
python-support
python-newt
mtools
mtr-tiny
finger
libustr-1.0-1
libsemanage1
libdb4.7
Is there any rationale from these internal discussions about why these tools
have been demoted? It's hard to refute an argument that hasn't been
presented.
It was a discussion taking some time with us looking at the packages and
then seeing how many of us are in favour.
The policy
We already have these packages:
fdupes
perforate
AFAIK, they do not replace files, they just find them.
Wrong, fdupe from perforate does link them together if one wants to.
Imagine you have two backups, each on a different filesystem. Now you
want to have them both on one filesystem.
Hi
as announced a bit earlier[1], I just changed the frequency of our dinstall
run, and as such the frequency of the mirror pushes too.
We are now having 4 runs/pushes a day. The runs start at
[01|07|13|19]:52 (every 6 hours, starting at 1:52), the mirror push
follows approximately an hour
On 11603 March 1977, Manoj Srivastava wrote:
I am hereby resigning as secretary, effective immediately.
:( Sorry to hear that. Whoever is your follower *will* have a hard
time.
As to the people who emailed me that they are putting together a
petition for the DAM to have me
The only thing that's been seriously discussed with an eye to
implementation, so far as I know, is to automatically reject on the basis
of a hand-selected and very limited subset of Lintian tags, which would
probably not affect anything that you're doing and which would certainly
not
By what process will the selection of lintian tags be submitted to the
project for review and approval prior to implementation as a hard
reject?
I think that's a pretty good question. I don't think we need a very
formal process, but as a Lintian maintainer, I'd kind of like people to
I have a list of tags. In Extremadura I had other ftpteam members and a
lintian maintainer look at it. Whenever this gets implemented this list will
be made public and then have a place on ftp-master.d.o webpage
somewhere. And everyone can comment on it.
So it was already decided that it was
It surprises me that the only solution to that problem seems to be to
add more people to the FTP team, so that the processing bandwidth will
improve.
That is the only solution which will help.
That's not true.
Sre. And the world dies tomorrow.
We imposed that reviewing step to
Joerg Jaspert wrote:
someone that not only complains on lists but actually wants to do work.
just to make sure: is this targeted at me?
No.
--
bye, Joerg
My first contact with Linux was with SuSE 6.3. A friend of mine
installed it on my pc, and just take me a couple of hours to reinstall
On 11583 March 1977, Gerrit Pape wrote:
As i got asked for the complete text of the rejection mail, as the
thread start only had a partial quote, here it is.
--8schnipp-8---
From: Joerg Jaspert [EMAIL PROTECTED]
Subject: netqmail_1.06
There currently isn't a ban in place.[1] [...]
1: Thankfully, it hasn't been required yet
I am confused:
And because of that I've asked the listmasters to block him from
posting to d-d-a.
Where is the truth?
The truth is that you cant read or parse english. :)
I've asked is not I told
Hi
with the next mirror run the /tools directory will be gone from Debian
mirrors.
It contained *old* tools to help DOS users to install Linux and AFAIk
wasn't really used for anything anymore anyway. And noone complained
when I asked about it in August this year, so now its gone.
In case
And noone complained when I asked about it in August this year, so now
its gone.
Uh, I wasn't yet subscribed to debian-devel at the time and thus
wasn't aware of that goal. It sure is still useful for blind people
booting from a DOS bootdisk with a screen reader (still so far the only
Hence the question goes as: considering that the next release of
Debian is most likely going to be released with Emacs (= 23.1), which
is integrated properly with EasyPG, do we need alpaca in Debian? I
believe the answer is «no».
I think that the alpaca package isn't meaningless even if
On 11548 March 1977, Tatsuya Kinoshita wrote:
How about integrating/merging alpaca into EasyPG?
Anyway, alpaca is a different implementation and well maintained by
the other developer. I think that the alpaca package isn't
meaningless even if less people use alpaca than EasyPG.
There is the
On 11536 March 1977, Norbert Preining wrote:
On So, 12 Okt 2008, Adeodato Simó wrote:
http://db.debian.org/doc-mail.html
Thanks. Was it always like that that changes could only be made vie
email? I don't remember doing that, but then it was quite some time ago.
This way exists for *years*
Please always only use the symbolic names for the places to upload to
(ie ftp.upload.debian.org and ssh.upload.debian.org), do not use any
machine name directly. Queues may move at any time, without further
notice and the symbolic names will be updated.
What conceivable reason is there
Instead, you seem to be saying, how could anyone be so stupid as to use
a non-symbolic name? when nobody is actually being that stupid. We're
just using the symbolic name we were told to use the last time the names
were changed.
I never intended to say that and my initial mail didnt do that
Please always only use the symbolic names for the places to upload to
(ie ftp.upload.debian.org and ssh.upload.debian.org), do not use any
machine name directly. Queues may move at any time, without further
notice and the symbolic names will be updated.
What conceivable reason is there for
On 11514 March 1977, Mike Hommey wrote:
To untie the upload queue from the archive DSA setup an alias to be used
for future uploads. Please change your configuration of dput, dupload or
whatever you use to no longer use ftp-master.debian.org but
ftp.upload.debian.org instead.
Are default
On 11514 March 1977, Julien Cristau wrote:
1) I use Tollef's DELAYED queue mostly for 0-day because it's accessible
over ssh, so I can rsync files over which is more reliable than ftp on a
bad link. It sounds like you're removing the possibility to use that (I
know I can rsync files to some
On 11514 March 1977, Faidon Liambotis wrote:
Joerg Jaspert wrote:
Only problem is - if someone goes and uploads a NEW package there it
would get us in trouble, as we would distribute it before it got its
inspection if we really can do that. So if that ever happens it needs
some extra code
| Perhaps the DELAYED queue should be moved out of ~tfheen to a more
| neutral directory?
| ACK on all this request, which I was going to write almost identically :-)
| Cc-ing ftpmaster.
| We sure can move it back into ftpmasters hands sometime in the not too
| distant future.
I just
Perhaps the DELAYED queue should be moved out of ~tfheen to a more
neutral directory?
ACK on all this request, which I was going to write almost identically :-)
Cc-ing ftpmaster.
We sure can move it back into ftpmasters hands sometime in the not too
distant future.
--
bye, Joerg
Some NM:
If
On 11478 March 1977, Steve Langasek wrote:
- If an architecture fails to be included in 2 successive official
releases, it is moved out of the official archive (and away from the
ftp-master.debian.org host).
- We (as in ftpteam) are happy to help in any possible way in a move
Hi
unless someone has a *very* good reason (and is willing to do the work)
we are planning to kick the tools/ directory from our mirrors, as well
as the dftp*.gz files in project/misc.
Reason:
- They are useless nowadays. If someone wants to install Debian from a
windows system they use some
Hi
currently our archive has the feature(?) that a source package in component a
(like main) can build a binary package in component b (like contrib).[1]
Now, this feature is blocking (or making it way harder) to do some
database re-designs we want to do for the central archive database, so
we
Hi
as we are currently planning database changes en masse to the projectb,
please, everyone that is using the database (via its copy on merkel
mostly, i think):
Please login to merkel and add yourself to ~joerg/projectb.users (the
file is mode 666, so everyone with login is able to do it).
List
On 11454 March 1977, Charles Plessy wrote:
*) I assume that the priority of -dbg packages is extra
s/I assume that//
s/$/!/
Does it mean that not being extra is a bug, that the persons with
write access to the `override' file will systematicly set the priority
of -dbg packages to `extra',
Heya World,
I just did the requested switch, sysklogd/klogd are now priority extra,
rsyslog (not its -mysql -pgsql packages) are now priority important.
If something else, like Tasks or so, needs to be changed too: Whoever
needs to do that please do it. Thanks.
--
bye, Joerg
[ New Maintainer
On 11439 March 1977, Theodore Ts'o wrote:
*) I assume that the priority of -dbg packages is extra
s/I assume that//
s/$/!/
*) What section should -dbg packages be placed into? Should it be the
section that the parent package is in, or something like devel?
Currently usually the same as
On 11424 March 1977, Francesco Poli wrote:
Important disclaimers: IANAL, TINLA, IANADD, TINASOTODP.
Those are *totally* and absolutely unimportant and a waste to write.
Could people please stop always writing them, its fairly clear by itself
that debian-legal does NOT do any lawyers work (and
On 11412 March 1977, William Pitcock wrote:
So, in a nutshell, nobody in the current IRCd development community
cares about perceived GPL+OpenSSL compatibility issues, so only Debian
does, which is ok, but that's not so useful when Debian is already
shipping packages linked against OpenSSL
On 11404 March 1977, Mike Bird wrote:
Artificially lowering the RC count in Testing is not always
preferential to keeping Testing in a state amenable to testing.
You say yourself that it's not artificially as RC bugs in new packages
don't get that easily in testing anymore...
Removing
On 11401 March 1977, Raphael Hertzog wrote:
Some time after this mail we will give a few tasks to those who
volunteer to test their ability and then (maybe) have a few new members
in our team in the not too distant future.
I would suggest that developing a patch for
Hi,
one important question lately has been What should we do with large
packages containing data, like game data, huge icon/wallpaper sets,
some science data sets, etc. Naturally, this is a decision ftpmaster has
to take, so here are our thoughts on it to facilitate discussion and see
if we
On 11397 March 1977, Charles Plessy wrote:
I have a question about the sources: for big datasets, would it be
acceptable that the source package does not contain the data itself but
only a script to download it? Since the source packages are not to be
autobuilt and the binary packages only
On 11387 March 1977, Martin Uecker wrote:
Nevertheless, the right thing in my opinion would have been to
propose a patch, wait until it is accepted, and then to package
the new upstream version.
If you want that - build an own distribution. Or well - an LFS.
Because thats *not* what a
On 11382 March 1977, Neil Williams wrote:
Package: general
Severity: normal
User: [EMAIL PROTECTED]
In preparation for a pseudo-package, buildd.emdebian.org, I'm filing
Yes, as flooding -devel with lots of useless stuff (for -devel) is *THE*
way to get those responsible for pseudo packages
On 11379 March 1977, Cameron Dale wrote:
Is that a bug, or were my assumptions wrong? FWIW, I think using real
(not pseudo) mail headers is a mildly better solution, but I'm happy
either way.
Bug, should be in (real) headers. :)
--
bye, Joerg
Karnaugh Guy I wrote this thing but it really
On 11378 March 1977, Peter Eisentraut wrote:
I think it would be very nice to press these into some common form, such as
X-Debian: BTS
X-Debian: DAK
X-Debian: PTS
X-Debian: BTS-link
Maybe there is a quasi-standard for constructing these X- headers.
While I think most of daks mails do have
On 11375 March 1977, Dirk Eddelbuettel wrote:
As an alternative, could I just start from Ra source, and then in
debian/rules obtain r-base's orig.tar.gz, untar it and then apply the Ra
sources to it? Or is that too fragile?
No. Do not assume that there is *any* network connectivity at build
On 11361 March 1977, Christian Perrier wrote:
I happen to often send mails to package@packages.debian.org while
conducting my NMU campaigns for l10n bugs hunting.
From time to time, I still get such mails rejected because the said
package uses a mailing list as Maintainer:.
I did hate that
On 11348 March 1977, Christoph Haas wrote:
This does not need to happen before fall 2008. But then it would be nice
if we could move it then. Who is in charge of the debian.org servers for
this matter?
Who would have guessed - its DSA, the admins of our machines.
--
bye, Joerg
Ganneff kde
On 11348 March 1977, Christoph Haas wrote:
As soon as that part is done I would like to consider moving the service
to an official Debian machine. I've been sponsoring hardware for
mentors.debian.net for the last years. In my opinion the mentors server
has become an established resource and
On 11348 March 1977, Christoph Haas wrote:
One problem with hosting it on a debian.org machine is that this might
include software not checked by an ftpmaster/assistant, which might very
well be undistributable by Debian. Which is a *BAD* thing to do on a
debian host. IMO not very likely to
On 11320 March 1977, José L. Redrejo Rodríguez wrote:
Description : Free fonts for education and institutions
This package will provide free true type fonts that have been developed
by Juan José Marcos and, later, donated to the gnuLinEx project.
These fonts are very focused on
On 11311 March 1977, Romain Beauxis wrote:
Hey, reading you I figured out that all newcomers are required to have
contributions in Debian, which means *new packages*.
No, it doesn't mean new packages. It means contributions.
--
bye, Joerg
A.D. 1517:
Martin Luther nails his 95 Theses to the
Package: wnpp
Severity: wishlist
* Package name: pytrainer
Version : 1.5
Upstream Author : Fiz Vazquez [EMAIL PROTECTED]
* URL or Web page : http://pytrainer.e-oss.net/
* License : GPLv2
Description : Free Sport Training Center
Pytrainer is a tool to log your
Package: wnpp
Severity: wishlist
* Package name: garmintools
Version : 0.05
Upstream Author : Dave Bailey [EMAIL PROTECTED]
* URL or Web page : http://code.google.com/p/garmintools/
* License : GPLv2
Description : A Linux interface to the Garmin Forerunner GPS units
On 11303 March 1977, David Paleino wrote:
Ehm... using a better wording?
I wont. Its an RFP, and I just copied the text from upstreams
homepage. Whoever packages it might take whatever they want.
--
bye Joerg
exa And mind you, I have always been respectful to every debian
developer
On 11293 March 1977, Thomas Viehmann wrote:
somewhere else etc. to map key fingerprints to Debian accounts. Add
@debian.org
and you get an email address (let's not care about people disabling
it).
ANY solution *HAS* to care about this, there is no way you can sanely
think that [EMAIL
On 11293 March 1977, Philippe Cloutier wrote:
Lets jump in here, even if not all points address your mail only.
If by disfavour you imply that it's intentional that NEW packages
aren't built before being accepted, I think you're wrong. I think it
would require not completely trivial changes.
On 11286 March 1977, Thomas Goirand wrote:
I saw that there is now a new debhelper package version 6 in SID. I have
been told by my sponsor to have a dependency to it, and set my
compatibility level to 6. This is quite ok, but I need to maintain my
package for Etch. I did a quick backport of
[forced change to debhelper v6 compat]
Do not follow the advice of that sponsor, look for a different sponsor
instead. Only ever update the debhelper dependency if you really use a
feature of the new version.
Now, as this raised some comments on IRC, lets clarify it a bit:
- compat mode v1
On 11286 March 1977, Roberto C. Sánchez wrote:
In any event, perhaps the advice you provide in your other mail in
this thread should be included in the Debian developer reference.
Want to write the wishlist bugreport?
--
bye Joerg
Debian is about free speech. beer once brewed can no longer
On 11278 March 1977, Roger Leigh wrote:
http://ftp-master.debian.org/bzr/
Why isn't this on bzr.debian.org?
Why should it be there?
Its in /srv/ftp.debian.org on the ftp-master host, *the* central place
for all ftpmaster related things.
--
bye Joerg
SUSE = Soll Unix Sein, Eigentlich.
--
On 11278 March 1977, Holger Levsen wrote:
So we decided to switch to syslog-ng for now.
On the #debian-release channel some people claimed, that syslog-ng is not a
drop-in replacement, while other said so. I don't know :) Please explain
here. Other options would be rsyslog (which Fedora
Package: wnpp
Severity: normal
Hi
i want to get rid of this package. Want it? Take it, but careful, its
Upstream is JS. If noone in a week or so - removing is also nice.
Package: smake
Priority: optional
Section: devel
Installed-Size: 268
Maintainer: Joerg Jaspert [EMAIL PROTECTED
301 - 400 of 815 matches
Mail list logo
