On 02/20/2015 06:25 AM, Harald Dunkel wrote:
Hi Daniel,
On 02/20/15 13:09, Daniel Leidert wrote:
Just to understand your problem: there is a package foo. Debian provides
it with version 1:A-B and upstream provides some self-compiled packages
with the same name under version C-D (and C-D
On Tue, Feb 24, 2015 at 05:10:40PM +, Ian Jackson wrote:
Jonathan Dowland writes (Re: conflicts between Debian's and upstream's
Debian package):
The bad packages Harald is talking about, I think, are external to
Debian — I don't think he's trying to protect a DD here. So
Quoting Harald Dunkel (2015-02-24 15:09:15)
On 02/20/15 18:54, Andreas Tille wrote:
Is there any reason why you do not even now are talking about package
name and upstream URL featuring the same name? Its not fruitful to
leave your discussion partners in the dark.
Sorry, but I don't
Hi Andreas,
On 02/20/15 18:54, Andreas Tille wrote:
Hi Harald,
Is there any reason why you do not even now are talking about package
name and upstream URL featuring the same name? Its not fruitful to
leave your discussion partners in the dark.
Sorry, but I don't want to blame anybody
On 02/24/15 15:09, Harald Dunkel wrote:
Sorry, but I don't want to blame anybody producing bad packages.
It shouldn't matter here.
Should be:
Sorry, but I don't want to blame anybody to produce bad packages.
Name and upstream URL shouldn't matter here.
Sorry for my bad English.
Regards
On Tue, Feb 24, 2015 at 03:55:35PM +0100, Jonas Smedegaard wrote:
I disagree: We won't hide problems.
(Sure I agree that we shouldn't throw blame, but that's on you to
collide those two, not me)
The bad packages Harald is talking about, I think, are external to
Debian — I don't think he's
Jonathan Dowland writes (Re: conflicts between Debian's and upstream's Debian
package):
The bad packages Harald is talking about, I think, are external to
Debian — I don't think he's trying to protect a DD here. So this is
courtesy rather than hiding problems.
I don't think reference
On Sat, Feb 21, 2015 at 12:48:02PM -0800, Cameron Norman wrote:
El vie, 20 de feb 2015 a las 12:04 , Harald Dunkel ha...@afaics.de
escribió:
Hi folks,
I would like to use upstream's Debian/Ubuntu packages for a certain
tool 'foo'. Its closer to what I need, and I don't have
Am Freitag, den 20.02.2015, 18:54 +0100 schrieb Andreas Tille:
[..]
Is there any reason why you do not even now are talking about package
name and upstream URL featuring the same name? Its not fruitful to
leave your discussion partners in the dark.
Well, Debian has made decisions against
On Fri, 20 Feb 2015 22:15:41 +0100
Marc Haber mh+debian-de...@zugschlus.de wrote:
On Fri, 20 Feb 2015 09:04:56 +0100, Harald Dunkel ha...@afaics.de
wrote:
Problem: The Debian maintainer messed up the version numbers
and had to introduce a 1: for his foo package. Now upstream's
package
On Fri, 20 Feb 2015 19:31:49 +0100
Adam Borowski kilob...@angband.pl wrote:
On Fri, Feb 20, 2015 at 05:53:27PM +, Simon McVittie wrote:
If the Debian packages are not as good as the upstream ones, such
that you end up having to use the upstream ones for some reason,
then that also
El vie, 20 de feb 2015 a las 12:04 , Harald Dunkel ha...@afaics.de
escribió:
Hi folks,
I would like to use upstream's Debian/Ubuntu packages for a
certain tool 'foo'. Its closer to what I need, and I don't
have migrate between both versions before asking the mailing
list for help or for
Hi Harald,
On Fri, Feb 20, 2015 at 09:04:56AM +0100, Harald Dunkel wrote:
I would like to use upstream's Debian/Ubuntu packages for a
certain tool 'foo'. Its closer to what I need, and I don't
have migrate between both versions before asking the mailing
list for help or for
On Fri, Feb 20, 2015 at 09:04:56AM +0100, Harald Dunkel wrote:
Hi folks,
I would like to use upstream's Debian/Ubuntu packages for a
certain tool 'foo'. Its closer to what I need, and I don't
have migrate between both versions before asking the mailing
list for help or for
Hi,
On Fri, Feb 20, 2015 at 01:09:20PM +0100, Daniel Leidert wrote:
...
These are the ways, I would try.
While this perfectly answers to question of the original poster it is
hiding a potential problem inside a (currently unknown) Debian package.
Harald, in case you follow this hint, please
Hi Daniel,
On 02/20/15 13:09, Daniel Leidert wrote:
Just to understand your problem: there is a package foo. Debian provides
it with version 1:A-B and upstream provides some self-compiled packages
with the same name under version C-D (and C-D 1:A-B) and you want to
force apt to install the
On Fri, 20 Feb 2015 09:50:13 +0100, Andreas Tille andr...@an3as.eu
wrote:
I have no idea why you concluded that the Debian package exists since
upstream is not good enough. Usually it is better to include a Debian
package into official Debian since you are profitting from several QA
means which
On Fri, 20 Feb 2015 09:04:56 +0100, Harald Dunkel ha...@afaics.de
wrote:
Problem: The Debian maintainer messed up the version numbers
and had to introduce a 1: for his foo package. Now upstream's
package always appears to be out of date, forcing me to override
apt-get.
That is unfortunately a
On Fri, Feb 20, 2015 at 03:25:32PM +0100, Harald Dunkel wrote:
On 02/20/15 13:09, Daniel Leidert wrote:
Just to understand your problem: there is a package foo. Debian provides
it with version 1:A-B and upstream provides some self-compiled packages
with the same name under version C-D
Hi Marc,
while your argument is true and known we have no idea what Harald really
means and thus we are wasting time in wild speculations. :-(
Kind regards
Andreas.
On Fri, Feb 20, 2015 at 10:15:41PM +0100, Marc Haber wrote:
On Fri, 20 Feb 2015 09:50:13 +0100, Andreas Tille
On 20/02/15 14:25, Harald Dunkel wrote:
IMHO there should be a policy for the special case, that
there is a naming conflict between upstream's source or
binary packages, and the packages included in Debian.
Whatever we might say on the subject in Debian policy, upstream-produced
packages are
Hi Harald,
On Fri, Feb 20, 2015 at 03:25:32PM +0100, Harald Dunkel wrote:
Just to understand your problem: there is a package foo. Debian provides
it with version 1:A-B and upstream provides some self-compiled packages
with the same name under version C-D (and C-D 1:A-B) and you want to
On Fri, Feb 20, 2015 at 05:53:27PM +, Simon McVittie wrote:
If the Debian packages are not as good as the upstream ones, such that
you end up having to use the upstream ones for some reason, then that
also seems like a bug. If you can help the Debian maintainer to fix that
bug (e.g. by
23 matches
Mail list logo
