Hi,
On Mon, Apr 14, 2014 at 05:12:32PM +0200, Matthias Klose wrote:
> it would be much more productive for Debian if you wouldn't claim wrong things
> and start fixing the issue in at least this package.
Just for the record: The bug is fixed but die to some additional changes
(providing data for
Wookey dixit:
> +++ Paul Wise [2014-04-16 19:51 +0800]:
> > On Wed, Apr 16, 2014 at 7:13 PM, Santiago Vila wrote:
> >
> > > What some people here try to do, update config.guess and related files,
> > > is, IMHO, just a hack. Sure, it will just work, but only for us (Debian).
[…]
> > Other distrib
Package: wnpp
Severity: wishlist
Owner: Andreas Tille
* Package name: varscan
Version : 2.3.6
Upstream Author : Dan Koboldt
* URL : http://varscan.sourceforge.net/
* License : NPOSL-3.0
Programming Lang: Java
Description : variant detection in next-gene
How to reconfigure one package from another?
I want to reconfigure packages from other packages.
Example:
* package foo-player
+ supports both JackD and PulseAudio, but only one
+ asks which method to use via debconf
* package bar-studio-desktop
+ depends on xfce4, jackd2 and foo
Le Thu, Apr 17, 2014 at 01:50:40PM +0200, Jonas Smedegaard a écrit :
> How to reconfigure one package from another?
>
> I want to reconfigure packages from other packages.
>
> Example:
>
> * package foo-player
> + supports both JackD and PulseAudio, but only one
> + asks which method t
Quoting Charles Plessy (2014-04-17 14:17:41)
> Le Thu, Apr 17, 2014 at 01:50:40PM +0200, Jonas Smedegaard a écrit :
>> How to reconfigure one package from another?
> If the maintainer scripts of the three packages can cooperate, have
> you considered using Dpkg triggers ?
Sorry if that was unclea
Package: wnpp
Severity: wishlist
Owner: Sebastien Badia
* Package name: ruby-faraday-middleware-multi-json
Version : 0.0.5
Upstream Author : Dennis Rogenius
* URL : https://github.com/denro/faraday_middleware-multi_json
* License : MIT
Programming Lang: Ruby
+++ Russ Allbery [2014-04-16 11:42 -0700]:
> Wookey writes:
>
> > So, where in debian should we put responsiblity for updating
> > config.{sub,guess}?
>
> I lean towards being more aggressive than this and running autoreconf or
> the moral equivalent on any package using Autoconf, by default.
Package: wnpp
Severity: wishlist
Owner: Sebastien Badia
* Package name: python-xmltodict
Version : 0.9.0
Upstream Author : Martin Blech
* URL : https://github.com/martinblech/xmltodict
* License : MIT
Programming Lang: Python
Description : Python modul
+++ Wookey [2014-04-17 15:20 +0100]:
> +++ Russ Allbery [2014-04-16 11:42 -0700]:
> > Wookey writes:
> >
> > > So, where in debian should we put responsiblity for updating
> > > config.{sub,guess}?
> >
> > I lean towards being more aggressive than this and running autoreconf or
> > the moral eq
Quoting Wookey (2014-04-17 16:20:09)
> +++ Russ Allbery [2014-04-16 11:42 -0700]:
>> What I'd therefore lean towards is for debhelper and CDBS (with a new
>> compat level) to automatically run dh-autoreconf if Autoconf was
>> detected but without depending on them, resulting in an immediate
>> F
Package: wnpp
Severity: wishlist
Owner: Sebastien Badia
* Package name: python-ncclient
Version : 0.4.1
Upstream Author : Leonidas Poulopoulos
* URL : http://ncclient.grnet.gr/
* License : Apache-2
Programming Lang: Python
Description : Python library
On Thu, Apr 17, 2014 at 03:20:09PM +0100, Wookey wrote:
> Also this doesn't fix things for packages using autoconf but not
> debhelper (whether via CDBS or not).
https://lists.debian.org/debian-devel-changes/2014/04/msg01249.html
Even Manoj, the most stalwart supporter of by-hand rules files, has
Jonas Smedegaard writes:
> Personally I would then silence the lintian warning, because...
> a) I dislike dh-autoreconf: It removes changed files which breaks my
> workflow where disappearing files are treated as an error.
> b) I prefer stripping automade files from source tarball, to avo
Hello,
It seems that in jessie (and similar in sid) a number of packages [1]
started to use ':' symbol in their dependency lists as part of package
names. This is, if I'm not misreading the Debian Policy §7.1 and §5.6.1,
is not allowed.
Suggestions for issue's severity and how to proceed?
[1] m
* Eugene V. Lyubimkin , 2014-04-17, 22:24:
It seems that in jessie (and similar in sid) a number of packages [1]
started to use ':' symbol in their dependency lists as part of package
names. This is, if I'm not misreading the Debian Policy §7.1 and
§5.6.1, is not allowed.
Suggestions for issu
* Jakub Wilk , 2014-04-17, 21:40:
* Eugene V. Lyubimkin , 2014-04-17, 22:24:
It seems that in jessie (and similar in sid) a number of packages
[1] started to use ':' symbol in their dependency lists as part of
package names. This is, if I'm not misreading the Debian Policy §7.1
and §5.6.1, is
FTR: I like running autoreconf to make sure actual sources are used, and
to document the build process for users who want to change any source
file, including Makefile.am etc.
On Thu, Apr 17, 2014 at 07:08:30PM +0200, Jonas Smedegaard wrote:
> a) I dislike dh-autoreconf: It removes changed files
* Bas Wijnen , 2014-04-17, 22:11:
On Thu, Apr 17, 2014 at 07:08:30PM +0200, Jonas Smedegaard wrote:
a) I dislike dh-autoreconf: It removes changed files which breaks my
workflow where disappearing files are treated as an error.
AFAIK this is incorrect. It will make backup copies during build,
* Steve Langasek:
> But I think we ought to switch to autoreconfing by default.
It's a bit risky if we don't do a mass rebuild after a new
autotools-related package upload. I still see quite a lot of warnings
if I re-run the tools on older sources, but these days, most builds
seem to work out al
* Russ Allbery:
> It's an interesting question whether we should just force
> dh-autoreconf in debhelper unless the package maintainer explicitly
> turns it off. It would save me work, just as I've now been able to
> take overrides back out of all of my packages now that dpkg defaults
> to xz com
Florian Weimer writes:
> It's a bit risky if we don't do a mass rebuild after a new
> autotools-related package upload. I still see quite a lot of warnings
> if I re-run the tools on older sources, but these days, most builds seem
> to work out alright.
Yeah, most of the warnings are about unde
Florian Weimer writes:
> * Russ Allbery:
>> It's an interesting question whether we should just force dh-autoreconf
>> in debhelper unless the package maintainer explicitly turns it off. It
>> would save me work, just as I've now been able to take overrides back
>> out of all of my packages now
Control: reassign -1 wnpp
On Jo, 17 apr 14, 23:20:24, Alessio Garzi wrote:
> Package: guake-indicator
> Version: 0.1-0~35~ubuntu13.10.1
> Severity: wishlist
>
> Guake-indicator is a C software application designed for Ubuntu 13.10 and
> 14.04
> with Unity that lets you manage your favorite ssh h
previously on this list Aaron Zauner contributed:
I agree with MACs being questionable in that they are an extra
*FINAL* layer only really effective on simple systems where they
arguably aren't needed, can be circumvented by kernel exploits and
often MACs are used on systems despite the wide rangi
Quoting Russ Allbery (2014-04-17 20:22:32)
> Jonas Smedegaard writes:
>
>> Personally I would then silence the lintian warning, because...
>
>> a) I dislike dh-autoreconf: It removes changed files which breaks my
>> workflow where disappearing files are treated as an error.
>> b) I prefer s
The following is a listing of packages for which help has been requested
through the WNPP (Work-Needing and Prospective Packages) system in the
last week.
Total number of orphaned packages: 573 (new: 9)
Total number of packages offered up for adoption: 133 (new: 0)
Total number of packages request
On Thu, Apr 17, 2014 at 7:50 PM, Jonas Smedegaard wrote:
> * package foo-player
> + supports both JackD and PulseAudio, but only one
> + asks which method to use via debconf
> * package bar-studio-desktop
> + depends on xfce4, jackd2 and foo-player
> + conflicts against bar-off
On Fri, Apr 18, 2014 at 4:49 AM, Florian Weimer wrote:
> The correct long-term fix is to change autotools to check a list of
> well-known paths for more recent versions of the scripts and use them
> instead of what is provided in the package.
Both the config.guess/sub and autoconf upstreams expli
On Thu, Apr 17, 2014 at 10:20 PM, Wookey wrote:
> Ben, are you following this thread? If you don't object violently to
> adding Paul's 'update from Debian canonical config.{sub.guess}
> locations by default' patch to the Debian autoconf, then that just
> leaves my original issue of what ensures th
Hi!
On Thu, 2014-04-17 at 22:24:11 +0300, Eugene V. Lyubimkin wrote:
> It seems that in jessie (and similar in sid) a number of packages [1]
> started to use ':' symbol in their dependency lists as part of package
> names. This is, if I'm not misreading the Debian Policy §7.1 and §5.6.1,
> is not
31 matches
Mail list logo