Package: wnpp
Severity: wishlist
Owner: Pierre Thierry
* Package name: elgrind
Version : n/a
Upstream Author : Isac Sacchi e Souza
* URL : https://github.com/isacssouza/erlgrind
* License : BSD-2-Clause
Programming Lang: Erlang
Description : Convert
For the nth time, I have a package that dpkg is unable to remove because
it tries to stop a service that either is already stopped (I didn't want
it) or couldn't start at all. In the former case, the fix seems simple:
start the service and remove the package. But sometimes starting the
service may
Is there available data about the overhead of enforcing various SELinux
policies?
Quantitatively,
Pierre
--
[EMAIL PROTECTED]
OpenPGP 0xD9D50D8A
signature.asc
Description: Digital signature
Scribit Neil Williams dies 13/11/2007 hora 17:02:
> If you want to build an ARM toolchain to crossbuild for amd64 I'm not
> going to stop you but don't expect me to debug it!!
But do your tools make it already possible for me to just ask for the
build of toolchains for an arbitrary list of target
Scribit Neil Williams dies 11/11/2007 hora 12:44:
> Emdebian supports amd64, i386 and powerpc as --build.
Why aren't all architectures supported by Debian supported?
Curiously,
Pierre
--
[EMAIL PROTECTED]
OpenPGP 0xD9D50D8A
signature.asc
Description: Digital signature
Scribit Josselin Mouette dies 09/11/2007 hora 22:53:
> BTW, there is another package which does this, and which is likely to
> cause you much more trouble: python. The build system compiles the
> modules using the generated python binary.
This is a classical problem in bootstrapping a language imp
Package: wnpp
Severity: wishlist
Owner: Pierre THIERRY <[EMAIL PROTECTED]>
* Package name: zpb-exif
Version : 1.0
Upstream Author : Zachary Beane <[EMAIL PROTECTED]>
* URL : http://www.xach.com/lisp/zpb-exif/
* License : BSD
Programming Lang:
Scribit Manoj Srivastava dies 09/10/2007 hora 00:04:
> It is kinda scary that my typical ./debian/rules has a minimum of 61
> targets, and that is just the base number. But it sure makes for
> pretty pictures :)
How did you generate those dependency graphs, BTW? I didn't find
anything relevant in
Scribit Michael Biebl dies 12/10/2007 hora 15:06:
> > - For packages where orphaning was proposed: 50 days
> > - For packages where removal was proposed: 100 days
> As sune suggested, 1 and 2 months would be enough imo.
As a compromise, the delay to orphan a package could be set to 1 month
when th
Scribit Roberto C. Sánchez dies 04/10/2007 hora 18:13:
> > wxWidgets has been released a long time ago and we're still missing
> > it.
> Yes, though for a good [1] reason.
Sure, wxwidgets has numerous bugs, but is it that surprising for a
library package that much used? (i.e. would such a backlog
Scribit Pierre Habouzit dies 03/10/2007 hora 21:49:
> *g* found exists and is versionned, since sth like a year now. if not
> two.
But is the submitter of the "found" information made easily available?
At least it's not shown anywhere in the version graph.
Curiously,
Pierre
--
[EMAIL PROTECTED]
Scribit Pierre Habouzit dies 02/10/2007 hora 20:16:
> Confirmed is not versionned. The fact that it was confirmed at one
> point does not means that the bug is still here.
Wouldn't a generic found-by be useful? Then the bug could contain the
information about not only the versions where the bug wa
Scribit Josselin Mouette dies 02/10/2007 hora 10:06:
> > Because it proves that we are fully self-hosting, and the main
> > reason _not_ to do it is the fear that we might _not_ actually be
> > self-hosting. Which is something I believe we've promised our
> > users, implicitly if not explicitly.
>
Package: wnpp
Severity: wishlist
Owner: Pierre THIERRY <[EMAIL PROTECTED]>
* Package name: bordeaux-threads
Version : 0.0.2
Upstream Author : Greg Pfeil
* URL : http://common-lisp.net/project/bordeaux-threads/
* License : MIT
Programming Lang: Commo
Package: wnpp
Severity: wishlist
Owner: Pierre THIERRY <[EMAIL PROTECTED]>
* Package name: cl-vectors
Version : 0.1.3
Upstream Author : Frédéric Jolliton <[EMAIL PROTECTED]>
* URL : http://projects.tuxee.net/cl-vectors/
* License : LLGPL
Prog
Package: wnpp
Severity: wishlist
Owner: Pierre THIERRY <[EMAIL PROTECTED]>
* Package name: mt19937
Version : 1.1
Upstream Author : Douglas T. Crosher and Raymond Toy
* URL : http://www.cliki.net/MT19937
* License : Public Domain
Programming Lang: Commo
Package: wnpp
Severity: wishlist
Owner: Pierre THIERRY <[EMAIL PROTECTED]>
* Package name: cl-salza-png
Version : 1.0
Upstream Author : Zachary Beane <[EMAIL PROTECTED]>
* URL : http://www.xach.com/lisp/salza-png.tgz
* License : BSD
Programming
Package: wnpp
Severity: wishlist
Owner: Pierre THIERRY <[EMAIL PROTECTED]>
* Package name: vecto
Version : 1.0.1
Upstream Author : Zachary Beane <[EMAIL PROTECTED]>
* URL : http://www.xach.com/lisp/vecto/
* License : BSD
Programming Lang:
Scribit Ian Jackson dies 29/06/2007 hora 14:28:
> I think it's a bug that we try to do upgrades from release A to B
> using A's packaging tools.
In most case, IME, it worked. In the cases where we know it won't,
couldn't the packaging tools be notified of the issue (much like the
"requires" file o
Scribit Greg Folkert dies 18/05/2007 hora 18:42:
> > It's so sad that these OT posters are driving away people like you.
> > [...]
> I guess you'd rather see the OT posters go away.
I guess not. It was explicitly acknowledged that killfiling OT posters
would prevent reading their useful posts, so
Scribit Michelle Konzack dies 25/04/2007 hora 20:44:
> > I think you're targetting the wrong layer of the system. If many
> > packages contain so much sensitive data, it would be easier to
> > encrypt a tarball or part of a FS where packages are read.
> The packages are in general on the Server!
C
Scribit Michelle Konzack dies 24/04/2007 hora 16:40:
> I would suggest to add a new header like "Crypted: " and then
> crypt the data.tar.gz (in the Debian package).
I think you're targetting the wrong layer of the system. If many
packages contain so much sensitive data, it would be easier to encr
Scribit Daniel Jacobowitz dies 23/04/2007 hora 16:19:
> Another possible way to change glibc would be to have libc6-dbg
> contain full debug symbols, libc6-dev contain -g1 symbols only, and
> have the -dbg divert the -dev.
Why not do that for every library?
Curiously,
Pierre
--
[EMAIL PROTECTED]
Scribit Ian Jackson dies 10/04/2007 hora 19:27:
> If the central package finds problems with the leaf package data it is
> usually more correct for only the inidividual leaf package to be
> recorded as not properly installed. There is not currently any way to
> do this and there are no plans to pr
Scribit Raphael Hertzog dies 15/04/2007 hora 14:07:
> The automatic dependency are mostly right and they are not a problem
> if a simple recompilation replaces them with a dependency that works
> within stable.
In the cases where this is only a matter of a simple recompilation,
maybe we should jus
Scribit Andrea Bolognani dies 12/04/2007 hora 18:01:
> I think a live CD aimed at developers would be quite useless. But
> feel free to correct me.
The Université Jussieu (Paris) found it useful. They distribute a live
CD based on Knoppix to the students, called Juppix:
http://www.pps.jussieu.fr
I was wondering, as I did not find any clear info on the subject by
Googling: is Debian the only distro that renamed the Mozilla packages?
If not, which ones?
Curiously,
Pierre
--
[EMAIL PROTECTED]
OpenPGP 0xD9D50D8A
signature.asc
Description: Digital signature
Scribit Samuel Mimram dies 22/03/2007 hora 18:10:
> * Package name: why
That's great! I had begun to play a bit with why, but having it as an
official Debian package will make it easier. As I'm beginning to do some
packaging, if you ever need it, I'd gladly help (packaging a new
upstream, tria
Scribit Steve Langasek dies 01/04/2007 hora 13:09:
> Hrm, is there really an RFC that specifies encryption before signing?
AFAIK, the RFC specifies how to build an encrypted MIME body and a
signed body. When you want both, you can either store a signed body in
the encrypted one, or an encrypted an
Scribit Magnus Holmgren dies 31/03/2007 hora 14:34:
> Have there been any discussion about adding a field to the Release and/or
> Packages files pointing at e.g. changelogs, so that aptitude etc. could
> display those for packages from unofficial repositories as well?
Maybe it would be worth des
Scribit Peter Samuelson dies 17/03/2007 hora 03:29:
> Linus Torvalds read Intel's announcement and was a bit disgusted that
> Intel tried as hard as they could to imply (without actually saying
> so) that the architecture was their own invention
Would you have any reference to this?
Curiously,
P
Hi,
I just discovered today that some packages can store pretty huge cache
data in my $HOME, and found that rather problematic. When I backup my
home, I don't want to waste backup space or time to do it, because I
have to check what eats space and tell if it's cache data.
Couldn't such packages,
Scribit Andreas Tille dies 06/12/2006 hora 14:09:
> > Please ignore paranoid people.
> To be honest you have to regard any nonencrypted mail as world
> readable and you can be nearly sure that all your mails are recorded
> at a place where you have no control over it.
I thought that very few ISP h
As I just installed an amd64 system, I discovered that the cmucl is not
already available for that port. If I'm not mistaken, cmucl needs some
manual bootstrapping.
Wouldn't it be useful to make it possible for a package needing
bootstrap to specify it, so that an unattended bootstrap be possible,
reassign 206293 mozilla-browser
reassign 173206 emacs21
reassign 202620 mozilla-browser
reassign 203700 ssh
reassign 246678 debtags
reassign 248664 bind9
reassign 173494 vim-gtk
reassign 199709 mutt
reassign 241866 jzip
reassign 248501 gman
reassign 206374 xml-resume-library
reassign 266021 ifupdow
Scribit Josselin Mouette dies 12/11/2005 hora 18:37:
> It was already suggested to accept only source+binary uploads, but to
> rebuild the binaries on the upload's architecture anyway.
Has there been a consensus on rejecting that solution?
Curiously,
Nowhere man
--
[EMAIL PROTECTED]
OpenPGP 0xD9
Scribit Manoj Srivastava dies 11/11/2005 hora 22:35:
> You gotta start trusting somewhere. Our web of trust starts with the
> Developers in the keyring, we trust these people not to muck with the
> binaries.
You trust them, but not any user of Debian will want to trust them so
much. Some will want
Scribit Anthony Towns dies 11/11/2005 hora 16:43:
> The problem is a technicality, not a moral or practical difference
> from the GPL's expectations: you still have the source to OpenSolaris
> libc, and you still have permission to modify it, redistribute it,
> sell it, etc.
Didn't someone ask for
Scribit Josselin Mouette dies 10/11/2005 hora 22:45:
> Le jeudi 10 novembre 2005 à 13:32 -0800, Debian Installer a écrit :
> > Rejected: source only uploads are not supported.
> I can't see the rationale for rejecting source uploads, and they used
> to be accepted in the past.
And I see a rational
Scribit Alex Ross dies 08/11/2005 hora 11:36:
> Overnight we actually did remove the downloads.
I'm downloading the LiveCD image right now from a link in the download
page[1]. Do I have to understand that you corrected the GPL violation
problem and that I can find all the sources the GPL gives me
Scribit Pierre THIERRY dies 08/11/2005 hora 01:04:
> * Package name: markdown
Sorry for that invalid ITP (markdown *is* packaged). It seems reportbug
check the archive when doing a RFP, but not an ITP.
Maybe on the supposition that when you do an ITP, you know more what
you're d
Package: wnpp
Severity: wishlist
Owner: Pierre THIERRY <[EMAIL PROTECTED]>
* Package name: markdown
Version : 1.0.1
Upstream Author : John Gruber <[EMAIL PROTECTED]>
* URL : http://daringfireball.net/projects/markdown/
* License : BSD-style
Scribit Kevin Mark dies 13/10/2005 hora 02:26:
> I was thinking of a feature that would show 'recommends' but add a
> line line explaining what installing package X would add to the
> currently selected package.
>
> [...]
>
> if this metadata could be added to the package data file it could be
> u
Scribit Stefano Zacchiroli dies 19/10/2005 hora 11:06:
> 1) once a bug as been closed - erroneously I would say - mailing
> [EMAIL PROTECTED] without the "Version:" pseudo header, is
> there a way to push the version information to the bts?
It seems. I did it for #297927: after sending a 'close 29
Scribit sean finney dies 16/10/2005 hora 11:00:
> also, i think extreme care should be take wrt these ssl certificates.
> i don't think they should be blindly purged at package removal (or
> probably even package purge) time, without getting permission from the
> local admin.
I think that this SSL
Scribit Christoph Berg dies 08/10/2005 hora 22:06:
> > Quickly,
> > Nowhere man
>
> Using realnames is a matter of politeness on Debian lists.
That's partly why my complete address in the From header of my mail is
Pierre THIERRY <[EMAIL PROTECTED]>
in
Scribit David Martínez Moreno dies 05/10/2005 hora 13:28:
> - Oh, yes. My package is only compiled for i386. O:-)
For the sake of my curiosity, aren't the packages in experimental taken
care of by the autobuilders?
Quickly,
Nowhere man
--
[EMAIL PROTECTED]
OpenPGP 0xD9D50D8A
signature.asc
Desc
Scribit Alban Browaeys dies 23/04/2005 hora 05:04:
> hum this is overkill. Install dwww (need an apache install) that s the
> best we have in debian until now.
The problem is also that many maintainers don"t register their
documentation with doc-base... Are there lintian/linda checks for
that ?
D
Scribit Don Armstrong dies 04/04/2005 hora 01:09:
> Otherwise, all you're doing is abusing the BTS, no matter how correct
> your actual appraisal of the severity bug is.
Downgrading a bug that is a clear violation of the policy just to have a
package in the next stable release IS abusing the BTS.
Scribit Steve Langasek dies 04/04/2005 hora 00:42:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=300765&msg=14
>
> He has the approval of the release team.
I didn't notice this mail in the time I was discussing with the
maintainer. And it lacks explanation. When I read it recently, I thought
Scribit Michael Schiansky dies 08/04/2005 hora 11:44:
> None of my maintained packages do provide such things. For all of them
> any automatic test is impossible as they require user interaction.
apt-get install expectk
> IMHO it's not worth the efford to implement such an autotest-system
> just
Scribit Miriam Ruiz dies 08/04/2005 hora 02:20:
> - Calculate days of "safe" sex
There are still people to believe that it works?!
Curiously,
Nowhere man
--
[EMAIL PROTECTED]
OpenPGP 0xD9D50D8A
signature.asc
Description: Digital signature
Scribit Steve Greenland dies 06/04/2005 hora 17:37:
> There's a long history of people relying on explicitly unspecified
> behaviour, and then bitching when that behaviour changes.
For the sake of my curiosity again, could you point me some precise
examples?
Historically,
Nowhere man
--
[EMAIL
Scribit Lars Wirzenius dies 06/04/2005 hora 21:34:
> > I don't find it very sane to be forced to deliberately trigger
> > problems on the user's system to find bugs.
> I assume the goal is to make it fail on the developer's system, on
> build daemons, whenever random developers unpack the package
Scribit Steve Greenland dies 04/04/2005 hora 07:15:
> > - what problems do thsi random order could weed?
> Unnoted dependencies that just happen to be fulfilled due to a
> consistent (though arbitrary) application order. By applying in a
> different order each time, you should trigger an error fair
Scribit Humberto Massa dies 04/04/2005 hora 10:46:
> > Cached? As in queried beforehand? As in two-pass algorithm, once
> > iterating init.d with 'depends' as option, then with 'start' ?
There are advantages to call the init.d script to poll its dependencies,
instead of reading them:
- the script
Scribit Adam Heath dies 01/04/2005 hora 19:10:
> Additionally, as a way to weed out other problems, any patches that
> are leafs(ie, don't depend on anything) are applied in a random order.
For the sake of my curiosity:
- what problems do thsi random order could weed?
- won't it be more difficult
I have a problem with a bug filed on r-doc-html (#300765). The
documentation was entirely in /usr/lib, and it seems that all R packages
have all their files under /usr/lib, whatever their type or purpose.
I filed a bug with severity serious, as this breaks Policy 9.1.1 (FHS is
mandatory). But the
> So looks like "sarge" above should be "woody".
Oh, yes. I was wondering why I found so few (!) packages, because last
time I installed a fresh sarge, some debconf screen told me I could
install something like 14K packages...
BTW, is there any other distrib that includes officially so many
packa
Scribit Anthony Towns dies 23/03/2005 hora 21:52:
> Pierre THIERRY wrote:
> >- Debian: 11 ports, 9157 packages (sarge) [17593 in sid]
> Hrm, where are those numbers from?
wc -l (modulo the first lines) of the allpackages.txt file on the
website
Quickly,
Nowhere man
--
[EMAIL PROTEC
Scribit Bas Zoetekouw dies 15/03/2005 hora 10:37:
> I find it a bit hard to believe that Debian isn't able to support 11
> architectures while for example FreeBSD and NetBSD seem to manage
> fine.
- FreeBSD: 6 ports, 12646 packages
- Debian: 11 ports, 9157 packages (sarge) [17593 in sid]
- NetBSD:
tag 296917 +patch
thanks
Hi,
following the discussion about this bug on debian-devel, with some late,
I looked quickly in the code of the debhelper package, and I think I
could understand it very fast (proof that it is written in a very
maintainable way), so I tried to write this patch. I don't m
> If not where should it be?
What about /usr/local/ or /var/opt/? The former seems
to be the best one, to me...
Quickly,
le Moine Fou
--
[EMAIL PROTECTED]
OpenPGP 0xD9D50D8A
pgprcp3ynRiSh.pgp
Description: PGP signature
> > As a submitter, would you feel satisified that you had just gotten
> > such a mail?
> Yes, I would. I would then know that I could fetch the new release to
> see if the problem was really fixed in this release.
I must agree with Adam, and IIRC, there has alreadu been said on that
list that it
Hi,
I'm trying to build a small dice roll library in C++, that I'll package
next. But I block on an error that seem to be a bug of the toolchain
with C++:
/usr/bin/ld: hello: hidden symbol `__dso_handle' in
/usr/lib/gcc-lib/i386-linux/3.3.1/crtbegin.o is referenced by DSO
I didn't find any bug
> Gaetan RYCKEBOER [...] doesn't appear to be listed in the list of NM
> applicants.
http://nm.debian.org/nmstatus.php?email=gryckeboer%40virtual-net.fr
Quickly,
le Moine Fou
--
[EMAIL PROTECTED]
OpenPGP 0xD9D50D8A
pgphGvK4vbu4R.pgp
Description: PGP signature
> As I may take some time to finish the package, I thought of avoiding
> duplicated work.
You could just tetitle the bug to an ITA, to avoid confusion.
Quickly,
le Moine Fou
--
[EMAIL PROTECTED]
OpenPGP 0xD9D50D8A
pgpQ1PcwXARXS.pgp
Description: PGP signature
Package: wnpp
Version: N/A; reported 2003-08-24
Severity: wishlist
* Package name: libw3c-logvalidator-perl
Version : 0.2
Upstream Author : Olivier Thereaux <[EMAIL PROTECTED]>
* URL : http://www.w3.org/QA/Tools/LogValidator/
* License : W3C Software license (BS
> How do I configure your script to restart apache when the power button
> is pushed?
Because it has nothing to do with shutdown, you just change
/etc/acpi/events/powerbtn, and modify it to action=invoke-rc.d apache
restart
Quickly,
le Moine Fou
--
[EMAIL PROTECTED]
OpenPGP 0xD9D50D8A
pgpffTsY
>> Tags: patch
> You forgot to attach it :-)
Shit. And the BTS doesn't seem to have noticed the patch tag...
> Event-handling from cardmgr, hotplug, usbmgr, acpid, apmd etc. are
> really useful to be able to be customised by power users.
I think I'm something like a power user, and I hate having
Tags: patch
> I've edited it, and I'd bet I'm not the only one who has a
> dog/cat/turtle/etc who keeps knocking the power button, resulting in a
> change to scheduling a shutdown in 1 minutes time :)
I think a very good coded script should use a config file in /etc. But
maybe it's a purist opini
> You think wrong. The user should be able to choose whether the power
> button triggers shutdown or suspend to disk, for instance.
But one shouldn't have to edit a shell script to do it. It should just
be necessary to edit a configuration file. Like modifying the action
value to something like /u
> I think at least the RCness of this bug is rather dubious, frankly. If
> the script is configuration
I don't think the script is meant to be edited... So it should be in
/usr/sbin.
Quickly,
le Moine Fou
--
[EMAIL PROTECTED]
OpenPGP 0xD9D50D8A
pgpjHl0gN4jh5.pgp
Description: PGP signature
> He doesn't think that it's an appropriate use of alternatives, since
> the tools are not compatible.
What about having a the ability to parse the original xplot data in your
xplot ?
Simply,
le Moine Fou
--
[EMAIL PROTECTED]
OpenPGP 0xD9D50D8A
pgpOCAxGBQub9.pgp
Description: PGP signature
74 matches
Mail list logo
