Package: afnix, aleph
Severity: serious
Justification: file conflicts between packages, policy violation
hi,
both afnix and aleph do ship several files of eachother but do not
conflict or add a diversion, thus fail to be installed on the same
environment:
Unpacking aleph (from
texmacs_1.0.6.9-1_sparc.changes uploaded successfully to localhost
along with the files:
texmacs_1.0.6.9-1.dsc
texmacs_1.0.6.9.orig.tar.gz
texmacs_1.0.6.9-1.diff.gz
texmacs-common_1.0.6.9-1_all.deb
texmacs_1.0.6.9-1_sparc.deb
Greetings,
Your Debian queue daemon
--
To
Accepted:
texmacs-common_1.0.6.9-1_all.deb
to pool/main/t/texmacs/texmacs-common_1.0.6.9-1_all.deb
texmacs_1.0.6.9-1.diff.gz
to pool/main/t/texmacs/texmacs_1.0.6.9-1.diff.gz
texmacs_1.0.6.9-1.dsc
to pool/main/t/texmacs/texmacs_1.0.6.9-1.dsc
texmacs_1.0.6.9-1_sparc.deb
to
Your message dated Thu, 01 Mar 2007 08:33:11 +
with message-id [EMAIL PROTECTED]
and subject line Bug#412366: fixed in texmacs 1:1.0.6.9-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Could I have some advice about the best way to fix this one please? Here's
a summary:
* The obsolete package aleph is supserseded by afnix.
* I've requested the removal of aleph from unstable (bug #389163).
* There is already another RC bug against aleph, as it conflicts with
tetex-bin.
I didn't
On Thu, Mar 01, 2007 at 09:14:42AM -, Paul Cager wrote:
Could I have some advice about the best way to fix this one please? Here's
a summary:
* The obsolete package aleph is supserseded by afnix.
* I've requested the removal of aleph from unstable (bug #389163).
* There is already
Michael Koch [EMAIL PROTECTED] wrote:
Add this to afnix:
Conflicts: aleph
Replaces: aleph
This should make it possible to have always one of them installed and
make afnix replace aleph on dist-upgrades.
Isn't
Provides: aleph
also needed?
Regards, Frank
--
Dr. Frank Küster
Single
Hi there,
I tried this scenario an it also crashes..
But on the console there was also this line:
Could not find 'drkonqi' executable.
So 'rekall' depends on kdebase-bin in which drkonqi is placed.. this
should be corrected.
So do you have 'kdebase-bin' installed and if not, is this
On Thursday 01 March 2007, Simon Effenberg wrote:
Hi there,
I tried this scenario an it also crashes..
But on the console there was also this line:
Could not find 'drkonqi' executable.
So 'rekall' depends on kdebase-bin in which drkonqi is placed.. this
should be corrected.
Frank Küster wrote:
Michael Koch [EMAIL PROTECTED] wrote:
Add this to afnix:
Conflicts: aleph
Replaces: aleph
This should make it possible to have always one of them installed and
make afnix replace aleph on dist-upgrades.
Isn't
Provides: aleph
also needed?
Regards, Frank
On Thu, Mar 01, 2007 at 09:14:42AM -, Paul Cager wrote:
Could I have some advice about the best way to fix this one please? Here's
a summary:
* The obsolete package aleph is supserseded by afnix.
* I've requested the removal of aleph from unstable (bug #389163).
* There is already
On Tue, Feb 27, 2007 at 10:39:50PM -0600, Sebastian P. Luque wrote:
I choose store in database and rekall crashes immediately after choosing
the type of database, no matter what it is (mysql, postgresql, the two I
use in my system). I get these message at the terminal (narrowed to what
I
Hi, I hate to be the one to mention this, but people continue to
talk about your weight issue and it just disgusts me. Whether you
know it by now, people are always chattering about each other at
work but you come up more than enough. I wasn't the happiest or
best-fit up until a year ago or
On Wed, Feb 28, 2007 at 10:41:25AM +0100, Lucas Nussbaum wrote:
Well, what I'm looking for is:
[A] People with good ideas of tests that would improve Debian's
quality, or Free Software's quality in general
[B] People willing to help with providing code for the tests, and
providing
On Thu, Mar 01, 2007 at 02:27:54PM +0100, Filippo Giunchedi wrote:
how about testing automatic dist-upgrades like stable-testing?
I love this idea: as a maintainer is quite a burden to take care of
this, a massive testing effort would help a lot of DDs out there!
of course this is not trivial
[opening a new thread, since it was the original idea]
On Thu, Mar 01, 2007 at 02:59:59PM +0100, Stefano Zacchiroli wrote:
I'm more worried about how you choose the environment you want to
dist-upgrade. Various criteria that come to my mind (braindump):
- base system only (pro: easy to set up,
On Thu, Mar 01, 2007 at 02:59:59PM +0100, Stefano Zacchiroli wrote:
I'm more worried about how you choose the environment you want to
dist-upgrade. Various criteria that come to my mind (braindump):
- base system only (pro: easy to set up, cons: tests a too small set of
package)
- \forall
17 matches
Mail list logo
