y objections? is there
> already a maintainer? can this packet be debianized?
lame cannot be distributed because of mp3 patent issues, nor can any
other mp3 encoder afaik.
--
Kind regards,
+-------+
| Bas Zoetekouw | S
> software changes.
Is there already policy on how this hardware detection should be
implemented?
--
Kind regards,
+-----------+
| Bas Zoetekouw | Si l'on sait exactement ce |
|| que l&
regards,
+-------+
| Bas Zoetekouw | Si l'on sait exactement ce |
|| que l'on va faire, a quoi|
| [EMAIL PROTECTED] | bon le faire?|
|
go).
--
Kind regards,
+-------+
| Bas Zoetekouw | Si l'on sait exactement ce |
|| que l'on va faire, a quoi|
| [EMAIL PROTECTED] | bon le faire?
ch packages do you find
unneeded and unused? A package that may be not useful for you may be
very useful for many others.
I agree with you that the many orphaned packages are a problem, but that
won't be solved by your proposal.
--
Kind regards,
+-------
n care of and not orphaned quickly), but
the old ones.
--
Kind regards,
+-----------+
| Bas Zoetekouw | Si l'on sait exactement ce |
|| que l'on va faire, a quoi|
| [EMAIL PRO
t would be nice if it could be done on
a per-package basis.
--
Kind regards,
+-------+
| Bas Zoetekouw | Si l'on sait exactement ce |
|| que l'on va faire, a quoi|
| [EMAIL
sal.
[1] There should indeed be a procedure to detect non-maintained packages
and ophan them. This should probably be done by the QA team. But
there should be policy about this, of course.
[2] This should of course also be done in some structural manner.
--
Kind regards,
+---
iving all packages multiple maintainers I find a bit far
fetched a solution.
--
Kind regards,
+---+
| Bas Zoetekouw | Si l'on sait exactement ce |
|| que l'on va faire, a quoi|
| [EMAIL PROTECTED] | bon le faire?|
|[EMAIL PROTECTED] | Pablo Picasso |
+---+
Kind regards,
+-------+
| Bas Zoetekouw | Si l'on sait exactement ce |
|| que l'on va faire, a quoi|
| [EMAIL PROTECTED] | bon le faire?
ainer address IMO.
Probably the script that generates this page is broken: it's a locally
built kernel using make-kpkg.
--
Kind regards,
+-------+
| Bas Zoetekouw | Si l'on sait exactement ce |
|-
ind regards,
+-------+
| Bas Zoetekouw | Si l'on sait exactement ce |
|| que l'on va faire, a quoi|
| [EMAIL PROTECTED] | bon le faire?|
|[EMAIL PROTECTED] | Pablo Picasso |
+---+
I meant was: the page was apparently generated from local data
(from a local /var/lib/dpkg/available perhaps?).
--
Kind regards,
+---+
| Bas Zoetekouw | Si l'on sait exactement ce |
|--
ything's OK: ยค, see ;-)).
Well, I get a little square here, but that's probably my own settings.
--
Kind regards,
+---+
| Bas Zoetekouw | Si l'on sait exactement ce |
|
ear goals - what is the target
> > audience or audiences of debian?
> The target audience is everyone who uses a computer.
OK, but that is not very clear a goal. What do we want with all those
people? Do we want them all to use Debian? If so, what should be done to
accomplish
Hi Adam!
You wrote:
> Sure, everyone agrees. This has been hashed over and over and over. Talking
> about it doesn't help. Solve the problem.
How?
--
Kind regards,
+-------+
| Bas Zoetekouw | Si l'on
detect which parts of Debian need
attention and in what part things go wrong.
--
Kind regards,
+---+
| Bas Zoetekouw | Si l'on sait exactement ce |
|| que l'on va faire, a quoi|
| [EMAIL PROTECTED] | bon le faire?|
|[EMAIL PROTECTED] | Pablo Picasso |
+---+
") should be asked.
--
Kind regards,
+-------+
| Bas Zoetekouw | Si l'on sait exactement ce |
|| que l'on va faire, a quoi|
| [EMAIL PROTECTED] | bon le faire?|
|[EMAIL PROTECTED] | Pablo Picasso |
+---+
em. Should I?
No, this shouldn't be a problem. I use the same here
(server:/tftpboot/www.xxx.yyy.zzz symlinked to
/export/netboot/machinename). That works quite well.
--
Kind regards,
+-----------+
| Bas Zoetekouw
> can mail [EMAIL PROTECTED] and so on...
Or how about just adding a simple procmail rule if you don't want the
ACK's?
--
Kind regards,
+-------+
| Bas Zoetekouw | Si l'on sait exactement ce |
|--
re
are no outstanding RC bugs, I assume there are dependency problems.
--
Kind regards,
+-------+
| Bas Zoetekouw | Si l'on sait exactement ce |
|| que l'on va faire, a quoi|
Hi Petter!
You wrote:
> [Bas Zoetekouw]
> > Is there anything I can do to get galeon included in woody? Since there
> > are no outstanding RC bugs, I assume there are dependency problems.
>
> Did you check
> http://ftp-master.debian.org/testing/update_excuses.html.gz#
t; I guess that if mozilla is fixed then galeon may be able to get in
> during the few days' window aj referred to.
OK. Since the build problems seem to be easily solved (see #141077), I
hope both mozilla and galeon can be included in woody.
--
Kind regards,
+---
port your
> problems to [EMAIL PROTECTED]
Are people working on the dutch translation of the installation? If not,
I could do it.
--
Kind regards,
+-------+
| Bas Zoetekouw | Si l'on s
in the
archive of the debian-devel mailing list at http://lists.debian.org.
BTW: the debian-policy mailing list is meant for discussions about new
debian policy. Your question is probably more on topic on the
debian-devel mailing list.
--
Kind regards,
+---
ind regards,
+-------+
| Bas Zoetekouw | Si l'on sait exactement ce |
|| que l'on va faire, a quoi|
| [EMAIL PROTECTED] | bon le faire?|
|[EMAIL PROTECTED] |
Hi Lasse!
You wrote:
> You are probably sick and tired of this topic, but ...
> IT'S A QUARTER YEAR ANNIVERSARY OF 4.2.0 RELEASE!
Congratulations. Now please return to your Redhat box.
--
Kind regards,
+-------+
| Ba
Package: wnpp
Severity: wishlist
Owner: Bas Zoetekouw
* Package name: zabbix-api
Version : 0.5.3
Upstream Author : Aleksandr Balezin
* URL : https://pypi.org/project/zabbix-api/
* License : LGPL
Programming Lang: Python
Description : implementation of
101 - 128 of 128 matches
Mail list logo
