sible that the Makefile.in in your package already contains a
variable that performs a role similar to the CDEBUGOPTS I added to
cgoban.
Richard Braakman
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
es.html.
As far as I know there are no special procedures for picking up an
orphaned package. I did it by simply informing [EMAIL PROTECTED] and
uploading a new version. It is probably a good idea to mail to
debian-devel before you start working on the package, but you've
already done that :-)
There's ~maor/masterfiles/mkcontents on master, but I don't know if
that is the script that was actually used to create them. It might
be a possibly-older copy.
Unfortunately, per-user crontab files are read-protected, so there's
no way to trace a path from the weekly cron job to the Contents fil
Michael Meskes wrote:
> How come this packaged hasn't been updated for a while. Since H.J. Lu is
> adding more and more libc6 compatibility changes I think it makes sense to
> stay up-to-date with libc5, too.
I haven't heard anything from Helmut Geyer in months, except for a
message on Sep 24 sayi
create for the shared libraries.
and:
If you do the above your package does not need to call ldconfig in its
maintainer scripts.
So, could this be something that should be fixed in libc6?
Why is it calling ldconfig?
Richard Braakman
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word
This is a list of packages in the main distribution that need work to
be fully libc6-based. I base it on the Packages file at my local mirror,
so it may be a day or two out of date. If you have questions about why
a particular package is on the list, or if you think there is an error,
don't hesit
; Why is it calling ldconfig?
>
> Because it's the Right thing to do.
Heh. That argument only convinces me if I already know why it's Right :-)
What does the ldconfig do, if the symlinks are already there?
Richard Braakman
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the wor
James Troup wrote:
> [EMAIL PROTECTED] (Richard Braakman) writes:
>
> > > The packaging manual is wrong; this is a long standing bug.
> >
> > Can you explain, or refer to a bug number that explains it?
>
> No. I have neither the time nor the inclination to tra
nt with all those other packages.
After all, it was only a nagging doubt.
Of course, we still need new text for the packaging manual. Try as
I might, I can not find a bug report to dpkg that addresses this.
Richard Braakman
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
David Frey wrote:
> On Sat, Dec 6 1997 21:50 +0100 Richard Braakman writes:
> > David Frey <[EMAIL PROTECTED]>:
> > pax-2.1-3(Not DFSG-compliant?)
>
> Hmm. I uploaded pax a few weeks ago into non-free (this was Mark H. Colburn's
> version)
Let&#x
This is a list similar to the "Libc6 progress" list, but for contrib
and non-free. Because source code is not available for many of these
packages, it will not be possible to convert all of them to libc6.
This list has had much less scrutiny than the other one, and is
therefore more likely to con
This is a list of packages in the main distribution that need work to
be fully libc6-based. I base it on the Packages file at my local mirror,
so it may be a day or two out of date. If you have questions about why
a particular package is on the list, or if you think there is an error,
don't hesit
cgoban, hextype, dutch
(idutch and wdutch), mpack, xconq (and xconq-doc), freeciv, and
maelstrom.
If there are any Debian developers (or developers-to-be) in
Gothenburg, I would love to meet them. Perhaps we can exchange PGP
key signatures as well.
Richard Braakman
--
TO UNSUBSCRIBE FROM THIS
g to make a non-maintainer
release of this magnitude myself.
Richard Braakman
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
This is a list of packages in the main distribution that need work to
be fully libc6-based. I base it on the Packages file at my local mirror,
so it may be a day or two out of date. If you have questions about why
a particular package is on the list, or if you think there is an error,
don't hesit
Yann Dirson wrote:
> Richard Braakman writes:
> > non-free: xforms0.86-0.86-2
>
> xmysql (contrib) is not listed, but depends on both libc6 and
> xforms0.86.
Ah, yes. That's a deficiency in the way I construct these lists.
Packages like xmysql will not show up until t
le the problem.
The main task of the compileall call in the postrm of these packages
is to remove the .pyc files of the python modules that have been
removed. One way to do this is to explicitly list the .pyc files to
remove. Another would be with a new option to compileall.py (only
delete, don&
.2.0f-22)
I took them from the latest libc5-dev in bo, which is 5.4.33-3. The
conflict/provide of libc-dev will make it conflict with libc6-dev (as
it should, since it installs files with the same names).
I'm attaching the new patch to this mail. Someone stop me if I
did something wrong
-altdev because the build process
referred to files in /usr/i486-linuxlibc1. I'm trying again now,
so it will take a couple of hours more.
Richard Braakman
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
compiled a libc5 hello-world program with the libc5-altdev package.
The other packages are completely untested; someone with a bo system
will have to do that.
I'm going to bed now, so I'll leave the rest to you :-)
Richard Braakman
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the w
ally linked.
--
I hope that someone can take this information and straighten it out to
turn it into a nice proposal for the policy manual.
Richard Braakman
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
Ben Gertzfield wrote:
[xforms0.86]
>
> I think this more than warrants a non-maintainer upload..
Heh, it wouldn't be a non-maintainer upload. If xforms 0.88 is
packaged, it will become a new package named xforms0.88. Whoever
packages it will simply be the maintainer of that packag
preferable, yes. It will make future releases much easier.
Perhaps you can ask Heiko Schlittermann for the source he used to
create the xforms0.86 .deb? That would save you some work.
Richard Braakman
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PRO
h 500 MB :-)
This way you'll miss the "native" packages. Is there a list of those?
Richard Braakman
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
tempt to configure
those packages right away; there is no reason not to try. (If
dependencies are not satisfied, it can try again after all packages
have been unpacked.)
Richard Braakman
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trou
er warn if you try to link a libc5 library with
a libc6 one, especially now that we're building a libc6 release.
Richard Braakman
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
'm assuming that the author will want to start numbering at 2 or 3,
because there are interface incompatibilities between ftplib-v1 and
ftplib-v2, and the current version is ftplib-v3).
Thanks,
Richard Braakman
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe"
I think you can find what you want in the cpp info file, node
"Standard Predefined". It lists macros like __DATE__ and __TIME__.
gcc itself also defines __FUNCTION__ and __PRETTY_FUNCTION__, which
behave more like string constants and can not be used in preprocessor
directives.
--
TO UNSUBSCRIB
this, like Guy Maor
described.)
Richard Braakman
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
t. (As far
as I know, there's no upstream maintainer for it either.)
It's currently in project/orphaned.
Richard Braakman
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
lking about.
Richard Braakman
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
ith libc6-dev (it installs
mostly the same files, so it has to). I don't know why it conflicts
with old libc versions. It replaces old ppp versions because it
replaces some files. (I remember an old bug report about that).
Richard Braakman
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the
elds?
If so, then I think it is far more effective to change dpkg's default
behaviour so that it does include these fields, rather than requiring
an explicit flag -isp.
However, I don't know the history behind this. What is the reason for
not including Section and Priority by default
There are a number of bug reports in the archive that were automatically
generated by a program named "deb-check". Is this program still around?
I would like to look at it.
Thanks,
Richard Braakman
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe"
Dale Scheetz wrote:
> On Tue, 6 Jan 1998, Richard Braakman wrote:
> > Do we want all packages to include the Section and Priority fields?
>
> Probably.
> >
> > If so, then I think it is far more effective to change dpkg's default
> > behaviour so that it
This is a list of packages in the main distribution that need work to
be fully libc6-based. I base it on the Packages file at my local mirror,
so it may be a day or two out of date. If you have questions about why
a particular package is on the list, or if you think there is an error,
don't hesit
(Consider how long it's taking to get the changelog and copyright
files named right in all packages)
- It will be one more thing that new maintainers can get wrong about
a package.
Richard Braakman
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscri
f we have no a.out development tools, how will we compile the
runtime support for a.out? The runtime support packages would
have to go into contrib.
Richard Braakman
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
and that causes dpkg to think that ppp
has overwritten all of ppp-pam.
Richard Braakman
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
This is a list of packages in the main distribution that need work to
be fully libc6-based. I base it on the Packages file at my local mirror,
so it may be a day or two out of date. If you have questions about why
a particular package is on the list, or if you think there is an error,
don't hesit
h my current scripts because they depend on the Contents file
generated on the master archive, which does not include non-us.
Richard Braakman
-=-
Change history:
Version 1998-01-09 (19 overlaps)
Removed entry f
Adam P. Harris wrote:
> "Richard" == Richard Braakman <[EMAIL PROTECTED]> writes:
[linking shared libraries against other libraries]
> > As far as I can tell, it does not save disk and memory space.
> > However, I am rather new at this. Feel free to correct
is better off with lftp than without, even if it has
this bug.
I recommend that you submit your mail as a bugreport for lftp.
Richard Braakman
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I have made a list of overlaps between packages in hamm and packages
in bo, and tried to filter out the ones that are not problematic.
(For example, because they use diversions).
My scripts for this are not always accurate, they're a bit old and
creaky. Unfortunately, there are too many overlap
Rev. Joseph Carter wrote:
> A question which comes to my curious mind... is there a way a program
> running as root can ask the kernel things like "do you support modules and
> module versioning?" or is the above script which hung my machine without
> so much as an oops from 2.1.82 till 2.1.89 the
lso find it disorienting to less a binary executable and get
a long list of identifiers. I _expect_ a screen full of garbage, and
that "/lib/ld-linux.so.2" in a particular position :-)
Richard Braakman
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
(0x40219000)
>
> this one even loads both libcs at the same time, without any LD_*
> environment variables. what to do?
Installing svgalib1 may help.
Richard Braakman
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
m making use of the
shipped-with-the-OS clause. (This closes a large loophole).
So if Motif is considered a standard part of the Red Hat OS, then
everyone *except* Red Hat can distribute such a program.
Richard Braakman
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubs
to fix
something that is broken.
Richard Braakman
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
east.
The introduction to s.9 also says "Debian's developers are currently
members of SPI by virtue of their status as developers". Is this
true? It would seem to depend on SPI's charter, not Debian's, and we
don't have that.
Richard Braakman
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
l suidregister
in the postinst, and use chown and chmod if suidregister is not available.
Lintian would have to parse that in order to get a full list, and it
doesn't do that (yet).
Richard Braakman
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe&q
making modifications to it".
Since the only modifications one might possibly want to make to
uedit all involve the use of the "rm" utility, which works just
*fine* on sources and executables alike, I see no obstacle to
placing this significant program in the main distribution.
Rich
pressive array of tclx packages, but tclx76
seems to be the last one we have. (I found no trace of tclx80).
The situation was a bit too complex for me to investigate today.
Richard Braakman
P.S. I now live and work in Helsinki, but I don't have an internet
connection at home yet (or, in fact,
I've installed tclx8.0.4
and removed tclx76.
The versions of tclx76 that I removed are still available in slink, so
I didn't put any in project/orphaned.
Richard Braakman
On Sat, Mar 11, 2000 at 12:07:11PM +0100, Christian Hammers wrote:
> Hello
>
> > Package: fetchmailconf (debian/main)
> > Maintainer: Paul Haggart <[EMAIL PROTECTED]>
> > [REMOVE] This package can be removed if it is not fixed.
> > 57287 generates wrong config files
> Hello!
>
> I fixed that
On Mon, Mar 13, 2000 at 12:42:54AM -0500, Daniel Martin wrote:
> Speaking of which, where did netdate go? I've been wondering for a
> while what happened to it.
It didn't actually have a license.
, it needs someone
to actually test it on the potato version, like you did.)
Richard Braakman
It really isn't
> release-critical in that sense.
Then it's not release-critical at all.
Richard Braakman
(presumably tested) new upstream version.
However, what else has changed in quota 2.00? Are there incompatibilities?
Richard Braakman
oblem specific to that version, which isn't
> in frozen (and may not even exist in unstable anymore..)
Okay, I'm excluding it from the list. Version 0.7-1 is in potato now,
and it's been compiled for all architectures.
Richard Braakman
On Wed, Mar 22, 2000 at 12:50:19PM +0100, Wichert Akkerman wrote:
> Previously Richard Braakman wrote:
> > Package: autofs (debian/main).
> > Maintainer: Justin Maurer <[EMAIL PROTECTED]>
> > 52132 autofs: Race condition when expiring autofs submounts leaves daemon
rt of Debian, and does not, per
> se, get released. I don't think that bugs on non-fee packages should
> be considered RC.
They are release-critical for that package.
In any case, I think we should have at least one working Netscape to go
with a release. It is a special case.
Richard Braakman
is worth dropping the package though.
Classic mistake. The "important" severity is misnamed. It doesn't mean
"this bug is important", it means "this package is unfit for release".
The bug was fixed today, though.
Richard Braakman
attention to the bug in some other way. Severity
"normal" does not mean "please ignore this bug until the sun goes out".
If you mark a bug release-critical, then that means I have to worry about
it, and have to make other people worry about it. Please don't do that
unless the bug really is critical to the release.
Richard Braakman
On Tue, Mar 28, 2000 at 01:20:33PM +1000, Anthony Towns wrote:
> tkirc (not installable on any arch, depends on ircii, which isn't in
> potato or woody)
ircii is now in non-us.
Richard Braakman
database and it will be useless. 200 release-critical bugs are
already too many to deal with. (We got 21 new ones just today.
Simply reading all of them takes more than an hour.)
Richard Braakman
The following packages have survived the bug horizon, in some cases twice,
because they are too important to drop. These bugs will delay the release
of potato.
Package: boot-floppies (debian/main).
Maintainer: Debian Install System Team
58266 [fixed in CVS] PCMCIA network install is broken
5
On Thu, Mar 30, 2000 at 03:17:17PM +0200, Adrian Bunk wrote:
> On Thu, 30 Mar 2000, Richard Braakman wrote:
>
> >...
> > Package: libgd-graph-perl (debian/contrib).
> > Maintainer: Piotr Roszatycki <[EMAIL PROTECTED]>
> > 59442 libgd-graph-perl:
On Thu, Mar 30, 2000 at 11:12:27AM -0800, Chip Salzenberg wrote:
> According to Richard Braakman:
> > Package: gcc (debian/main).
> > Maintainer: Debian GCC maintainers <[EMAIL PROTECTED]>
> > 58412 r-base: Can't build from source
> > 59819 gcc_2.95.2-7(fr
ow the decision ended up being made, but the argument
I presented at the time is that a dependency on debhelper is far more
likely to be versioned than the others are. A package that makes use
of a new feature of debhelper is going to have to declare its own
build-depends anyway.
Richard Braakman
matter of porting. We have
lots of unix-specific packages. I don't see a problem here.
Richard Braakman
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
d with an older version
of upx? The code I've seen doesn't seem to care much about that, so
I wonder if the author considers it a design requirement at all.
Richard Braakman
lly:
Package: snmpd
Description: NET SNMP (Simple Network Management Protocol) Agents.
The NET SNMP agent allows remote monitoring of various network and
system information.
This is a good enough explanation for me.
Richard Braakman
ss_ work for the user if you can have one xplot program
which replaces both of the current ones.
Richard Braakman
omething harmless
that reports the same errors.
Richard Braakman
n't have an interactive
configuration interface), I want to do it by creating a small,
human-editable file that contains the _differences_ from the defaults.
So even then I have no use for a copy of the default configuration.
(If I want an example, I can look in /usr/doc/$foo/examples, which is
a
ate it when
other developers do it. If the upstream changelog is verbose and
detailed (like the GNU ones tend to be) then it's nice to have the
major changes as a short list.
Richard Braakman
s it's generally
a bad idea, but the health of a free system depends on it being
potentially possible.
Richard Braakman
pload of a new package)
If you never got that email, then it's likely that there was something
wrong with the upload and the ftpmasters never saw it. Was it properly
signed, etc? Did it have a valid .changes file?
Richard Braakman
s if fixing bugs is some kind of privilege. These
people are *contributing* to Debian, despite the roadblocks we've
set up. The least you could do is show a bit of courtesy when they
complain that the roadblocks we've set up are inconvenient.
Richard Braakman
y useful? We already have the "Essential" flag to indicate
which packages are really required. We could just fold these
levels into one to simplify things.
Richard Braakman
greporter rudely pointed
out. Packaging that version would be a productive way to take over
this package :)
If you want it, please let me know, and (to avoid collisions) wait
for me to confirm before you actually make an upload.
Richard Braakman
act me and I'll happily
accept your offer to maintain it...
(If you're in the new maintainer queue, I'll also sponsor your
uploads as long as you don't make a mess of them.)
If I hear nothing about it in a week or two, then I'll assume
that everyone hates hextype and I'll ask for it to be removed.
Thanks,
Richard Braakman
On Sat, Jul 26, 2003 at 02:59:59PM +0200, Martin Godisch wrote:
> On Sat, Jul 26, 2003 at 14:59:50 +0300, Richard Braakman wrote:
>
> > One of the packages I "maintain" is cgoban. I packaged it ages ago when
> > I was a fanatical Go player. Nowadays I only get Go
seem much less effective now than when they started.
This might be because they're not eagerly being annotated anymore, though.
Richard Braakman
ges before we had
dpkg-statoverride.
Richard Braakman
, not the rule.
Of course, these days we have gnome and kde depending on every library
they can possibly find, and every other package depending on gnome
or kde (or both, if they can manage it), so the terrain may have
shifted somewhat...
Richard Braakman
ted for it afterwards, when the need for it has been demonstrated.
Richard Braakman
On Mon, Aug 04, 2003 at 12:42:27PM -0500, Adam Heath wrote:
> And of the users? Please read the social contract.
I read it every day, just before bedtime.
Richard Braakman
ams/ for later examination...)
Tab completion is fine in contexts where it works.
Richard Braakman
2. A person may hold several posts, except that the Project Leader,
Project Secretary and the Chairman of the Technical Committee must
be distinct, and that the Leader cannot appoint themselves as
their own Delegate.
Richard Braakman
t; messages are really pretty good, if you know how to filter for the key
> words.
No need to know that -- you can let google do it :) I often
paste whole error messages into the search field. It tends
to work.
Richard Braakman
laudable goals and you
want to contribute?
"Sure," you say, "then contribute. We'll just sit here and tell you
you suck. If after 6-48 months of being told you suck you still haven't
gone away, we'll think about officially (though grudgingly) accepting you."
On Fri, Aug 22, 2003 at 02:28:52AM +0200, Andreas Metzler wrote:
> Jérôme, please use "darn cabal of debian-legal zealots" next time.
>cu and- triple reading the original mail, stil smiling -reas
And don't forget to call them "licensing geeks"!
Richard Braakman
FSG, are the real
> consensus view.
???
The survey asks whether the GFDL _does_ satisfy the DFSG, not whether
it needs to. Did you misspeak here?
Richard Braakman
ckage
> which fixes some specific bug but leaves the package unmaintained.
> That's irresponsible.
That just doesn't make sense. Is it somehow more responsible to
skip the NMU and leave the package with an extra bug that you
could have fixed?
Richard Braakman
ng as much volunteer work as you think they
should be doing. That's rude.
Richard Braakman
If, on the other hand, you lean back in preparation for the accolades
and gratitude that you expect will follow, and you're already trying
to decide what kind of beer to accept, then your package is probably
ready for stable.
Richard Braakman
etent to recognize a mail as Sobig.F, which is
known to fake the sender, and then reply to it anyway. (And yes, I
get a lot of "notifications" that mention Sobig.F by name.)
Richard Braakman
would be right.
You're assuming that executables make up the bulk of most packages,
and that compression rates for those executables are similar. I highly
doubt both of those assumptions.
Richard Braakman
1 - 100 of 199 matches
Mail list logo
