Am 11.08.2011 19:12, schrieb Jonas Smedegaard:
My god, how can one be so ignorant and disrespectful as to not listen to
the arguments put forward (or ask if those are not understood).
Talking about arguments, I have two arguments in the form of users
that have reported real issues with the
On 11-08-12 at 09:27am, Fabian Greffrath wrote:
Your first argument was to blame the user for not using aptitude for
upgrades. This turned out as bullshit, because even aptitude does not
remove packages that still satisfy dependencies.
I apologize for adding irrelevant and distracting noise
People, please lets keep it civil.
On Fri, Aug 12, 2011 at 09:49, Jonas Smedegaard d...@jones.dk wrote:
You say that It is beneficial to Debian to keep package dependencies
as simple as possible. Generally I agree, but I'd also say it is even
more benefical to try as hard as possible not to
On 11-08-12 at 01:27pm, Felipe Sateler wrote:
People, please lets keep it civil.
Certainly. IF that remark was addressed to me, I would appreciate
having it spelled out how I failed to do so (in private email if you
prefer - I ask to honestly learn, not to discuss or claim innoscence).
On
Am 08.08.2011 09:38, schrieb Reinhard Tartler:
Does your proposed change to debian/pycompat fix it? If yes, just apply
the change and let's be done with it.
There was already a XS-Python-Version field in debian/control that
said all, which is obviously wrong when it fails with python2.3. So
On 11-08-11 at 11:24am, Fabian Greffrath wrote:
Am 08.08.2011 09:38, schrieb Reinhard Tartler:
Does your proposed change to debian/pycompat fix it? If yes, just
apply the change and let's be done with it.
There was already a XS-Python-Version field in debian/control that
said all, which is
Am 11.08.2011 11:34, schrieb Jonas Smedegaard:
No.
All versions (available in Debian) indeed satisfies the package needs.
My god, how can one be so stubborn!
___
pkg-multimedia-maintainers mailing list
On 11-08-11 at 01:21pm, Fabian Greffrath wrote:
Am 11.08.2011 11:34, schrieb Jonas Smedegaard:
No.
All versions (available in Debian) indeed satisfies the package
needs.
My god, how can one be so stubborn!
My god, how can one be so ignorant and disrespectful as to not listen to
the
Am 07.08.2011 13:08, schrieb Jonas Smedegaard:
I therefore see no reason to elevate this particular to be a general
issue for Debian.
I do. Are you fine with escalating this issue on -devel?
- Fabian
___
pkg-multimedia-maintainers mailing list
On 11-08-08 at 09:19am, Fabian Greffrath wrote:
Am 07.08.2011 13:08, schrieb Jonas Smedegaard:
I therefore see no reason to elevate this particular to be a general
issue for Debian.
I do. Are you fine with escalating this issue on -devel?
Not exactly fine - I find it annoying, but do what
Am 08.08.2011 09:38, schrieb Reinhard Tartler:
Does your proposed change to debian/pycompat fix it? If yes, just apply
the change and let's be done with it.
If not, what would need to be done to fix this properly? Then we could
start arguing if fixing it was worth the efford.
To be honest, I
Am 08.08.2011 10:44, schrieb Jonas Smedegaard:
We do not solve this issue by educating Debian packages more widely
about weird possible combinations of packages: Debian support upgrades
one stable release at a time - Debian do *not* support keeping around
old packages!
It is exact this point
On 11-08-08 at 11:07am, Fabian Greffrath wrote:
Am 08.08.2011 10:44, schrieb Jonas Smedegaard:
We do not solve this issue by educating Debian packages more widely
about weird possible combinations of packages: Debian support
upgrades one stable release at a time - Debian do *not* support
On 11-08-06 at 12:38pm, A. Costa wrote:
On Thu, 4 Aug 2011 14:23:20 +0200
Jonas Smedegaard d...@jones.dk wrote:
Closing *again* as a non-bug.
I follow, but here's my 2 cents from userland...
If a 'python2.3' package existed in the current Debian distros, then
this bug could be moved
On Thu, 4 Aug 2011 14:23:20 +0200
Jonas Smedegaard d...@jones.dk wrote:
Closing *again* as a non-bug.
I follow, but here's my 2 cents from userland...
If a 'python2.3' package existed in the current Debian distros, then
this bug could be moved to that package. No 'python2.3' package
currently
Am 28.07.2011 19:35, schrieb A. Costa:
For the record, I've had this same install bug for about a month, even
when installing with 'aptitude':
[...]
So the bug is real enough. Last month F. Greffrath advised:
Adding = 2.4 in debian/pycompat
Assuming that would help, why not do it?
Package: morituri
Version: 0.1.2-1
Followup-For: Bug #630787
For the record, I've had this same install bug for about a month, even
when installing with 'aptitude':
% aptitude install morituri ; echo $?
The following NEW packages will be installed:
morituri
0
17 matches
Mail list logo
