Hi Eugene,
> 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
Package: wnpp
Severity: wishlist
Owner: Michael Fladischer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
* Package name: django-polymorphic
Version : 0.5.4
Upstream Author : Bert Constantin
* URL : https://github.com/chrisglass/django_polymorphic
* License
Hi Paul,
I thought subject of my mail made my question clear:
How to reconfigure debconf from postinst of another package?
Quoting Paul Wise (2014-04-18 04:02:47)
> On Thu, Apr 17, 2014 at 7:50 PM, Jonas Smedegaard wrote:
>> * package foo-player
>> + supports both JackD and PulseAudio, b
Package: wnpp
Severity: wishlist
* Package name: libykneomgr
Version : 0.1.2-1
Upstream Author : Simon Josefsson
* URL : http://opensource.yubico.com/libykneomgr/
* License : LGPLv3+
Section : utils
This is a C library to interact with the Yub
Quoting Jonas Smedegaard (2014-04-18 00:32:23)
> 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 disapp
On 18/04/2014 12:43, Jonas Smedegaard wrote:
> Hi Paul,
>
> I thought subject of my mail made my question clear:
>
> How to reconfigure debconf from postinst of another package?
My opinion is that this is not allowed (but I did not checked explicitly
in Policy, so I may be wrong).
Calling re
Hi Kevin,
Kevin Chadwick wrote:
>
> However I do believe Debian and Linux should be doing a lot more
> outside of grsec/pax/gentoo hardened. I could be wrong but I'm under the
> impression that Ubuntu is ahead (maybe just as more bleeding edge and
> PAE by default etc. though I am surprised they
Hi Vincent,
Quoting Vincent Danjean (2014-04-18 14:41:18)
> On 18/04/2014 12:43, Jonas Smedegaard wrote:
>> How to reconfigure debconf from postinst of another package?
>
> My opinion is that this is not allowed (but I did not checked
> explicitly in Policy, so I may be wrong).
> Calling reco
Hi,
On 18/04/2014 00:15, Kevin Chadwick wrote:
> OpenBSD employs randomisation all over and recently starting with the
> boot loader.
I do not object to use such techniques (randomisation for example) by
default. However, it must be easy to disable them.
Indeed: not all computers are are us
On Fri, Apr 18, 2014 at 6:43 PM, Jonas Smedegaard wrote:
> Thanks, but (again) I am sorry if it was not clear: The *question* is
> about *debconf* irregardless of the *example* involving other details.
Examples are generally less useful than knowing the exact
circumstances that make you want a pa
On Fri, 18 Apr 2014 14:57:41 +0200
Aaron Zauner wrote:
> > Usually the Linux kernel itself provides more than enough entropy. This
> > can (and probably should) be enhanced but should not be done in a
> > specific distribution.
I know there has been a little work on the kernel in this area, main
+++ Russ Allbery [2014-04-17 14:24 -0700]:
> 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 t
Wookey writes:
> Can someone explain how this works, because so far as I can see this
> isn't true (well maybe 'most of the time' is true, but there is a
> non-trivial 'rest of the time' and we need to understand when/why that
> occurs, so we can make those DTRT too).
> The autoconf package (con
Quoting Paul Wise (2014-04-18 17:44:13)
> On Fri, Apr 18, 2014 at 6:43 PM, Jonas Smedegaard wrote:
>
>> Thanks, but (again) I am sorry if it was not clear: The *question* is
>> about *debconf* irregardless of the *example* involving other
>> details.
>
> Examples are generally less useful than kn
Hi folks!,
In addition to the various business card samples at
https://www.debian.org/events/materials/business-cards/, I slightly
modified the "traditional-new" version to have a two-sided version, with
an optional QR-code.
http://debian.httrack.com/card-traditional-new-2/
(Not sure if this is r
+++ Russ Allbery [2014-04-18 11:43 -0700]:
> Wookey writes:
>
> > Now I see that there is a copy of config.{sub,guess} in automake (in
> > /usr/share/automake-1.14/) so I guess that if automake is also used (or
> > maybe just installed?) then modern versions of these files will be found
> > and u
Wookey writes:
> It may be that libgc upstream's autogen.sh script is not really 'right'
> in some way. But there may well be a lot of upstreams like that, which
> is why maintainers need clear guidance on how to deal with this, without
> having to become autotools experts. i.e how to determine w
Paul Wise wrote:
>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 i
Am 19.04.2014 01:03, schrieb Russ Allbery:
>> OK, but again maintainers needs enough info to judge whether there is
>> something important in upstream's autogen.sh or if it's all effectively
>> boilerplate that a straighforward autoreconf will replace.
>
> I think what I'm arguing for is just run
On Sat, Apr 19, 2014 at 4:06 AM, Xavier Roche wrote:
> In addition to the various business card samples at
> https://www.debian.org/events/materials/business-cards/, I slightly
> modified the "traditional-new" version to have a two-sided version, with
> an optional QR-code.
> http://debian.httrack
On Sat, Apr 19, 2014 at 7:01 AM, Steve McIntyre wrote:
> Why? I've not seen any good arguments as to why they're right here.
It would be pointless. We are never going to have 100% of upstream
tarballs generated by the Debian version of autoconf and so we are
always going to need a mechanism in de
21 matches
Mail list logo
