Russ Allbery writes:
> David Kalnischkies writes:
>> On Thu, Feb 16, 2012 at 00:39, Russ Allbery wrote:
>
>>> Actually, why would that be the behavior? Â Why would dpkg --purge foo
>>> not just remove foo for all architectures for which it's installed, and
>>> require that if you want to remove
Serafeim Zanikolas writes:
> hi Goswin,
>
> On Wed, Feb 15, 2012 at 02:27:48PM +0100, Goswin von Brederlow wrote [edited]:
>> One thing though: Can I add my own local fragments? Is there a fragment
>> dir in /etc for that?
>
> you can, and they should also go to /usr/share/reconf-inetd (as long a
On 02/16/2012 12:22 AM, Serafeim Zanikolas wrote:
> hi Goswin,
>
> On Wed, Feb 15, 2012 at 02:27:48PM +0100, Goswin von Brederlow wrote [edited]:
>> One thing though: Can I add my own local fragments? Is there a fragment
>> dir in /etc for that?
>
> you can, and they should also go to /usr/share/
On Wed, Feb 15, 2012 at 11:12:28AM -0500, Filipus Klutiero wrote:
> Hum, interesting. I am aware that the ITS deals with errors in the
> package given, like when the user does a typo, but I'm not aware
> that one can "knowingly report against an unknown package". Could
> you explain how they would
On Wed, Feb 15, 2012 at 09:29:13PM +0100, Joachim Breitner wrote:
> Maybe the best we can do is to set good precedence for the next 100
> programming languages to come. Looking at some examples I find:
> * Haskell: Almost exclusively haskell-foo
> * OCaml: A mix of ocaml-foo, ocamlfoo a
Wouter Verhelst wrote:
> On Wed, Feb 15, 2012 at 11:12:28AM -0500, Filipus Klutiero wrote:
>> Hum, interesting. I am aware that the ITS deals with errors in the
>> package given, like when the user does a typo, but I'm not aware
>> that one can "knowingly report against an unknown package". Could
On Thu, Feb 16, 2012 at 09:41:40AM +0100, Goswin von Brederlow wrote [edited]:
[..]
> Putting local config into /usr/share is wrong though.
the answer to all local policy questions is: like you always did; you edit
inetd.conf.
/usr/share/reconf-inetd fragments are input to a *maintainer* tool. yo
On Thu, Feb 16, 2012 at 10:13:26AM +0100, Bernd Zeimetz wrote:
> On 02/16/2012 12:22 AM, Serafeim Zanikolas wrote:
> > hi Goswin,
> >
> > On Wed, Feb 15, 2012 at 02:27:48PM +0100, Goswin von Brederlow wrote
> > [edited]:
> >> One thing though: Can I add my own local fragments? Is there a fragment
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
Package name: eliom
Version: 2.0.2
Upstream Author: ocsigen team
URL: http://ocsigen.org
License: LGPL
Description: Eliom is a web framework for ocsigenserver written in OCaml.
--
To UNSUBSCRIBE, email to debian-dev
On Wed, Feb 15, 2012 at 11:12:28AM -0500, Filipus Klutiero wrote:
> Ah, OK. If the request is going to be "Why am I experiencing problem
> foo?", then it makes sense on debian-user. In that case, the problem
> is just phrasing (in the current phrasing, the user is already at
> the step of reporting
[Paul Wise, 2012-02-16]
> How about a lintian complaint at info/pedantic level called
> source-package-name-doesnt-match-binary-package that triggers on
> single-binary source packages and where the binary name doesnt look
> like a versioned library package?
Please don't. There are developers (lik
* Piotr Ożarowski , 2012-02-16, 12:59:
How about a lintian complaint at info/pedantic level called
source-package-name-doesnt-match-binary-package that triggers on
single-binary source packages and where the binary name doesnt look
like a versioned library package?
Please don't. There are devel
On Thu, Feb 16, 2012 at 09:26, Goswin von Brederlow wrote:
> Russ Allbery writes:
>> David Kalnischkies writes:
>>> On Thu, Feb 16, 2012 at 00:39, Russ Allbery wrote:
>>
Actually, why would that be the behavior? Why would dpkg --purge foo
not just remove foo for all architectures for
Package: wnpp
Severity: wishlist
Owner: Peter Palfrader
Description: pluggable transport proxy for Tor
obfsproxy is a tool that attempts to circumvent censorship, by
transforming the Tor traffic between the client and the bridge. This way,
censors, who usually monitor traffic between the clien
Le mercredi 01 février 2012 à 19:43 -0600, Steve M. Robbins a écrit :
>
>
> > Unfortunately they were still not available for that at the time of
> > my last poking. Diverging from upstream is not a good idea, so we
> > still have to live in a non perfect world...
>
> I think we can no longer l
Pierre Chambart:
> Package name: eliom
> Version: 2.0.2
> Upstream Author: ocsigen team
> URL: http://ocsigen.org
> License: LGPL
> Description: Eliom is a web framework for ocsigenserver written in OCaml.
Please also provide a long description.
Regards,
Thomas Koch, http://www.koch.ro
--
To
I was thinking more about this, and I was finally able to put a finger on
why I don't like package splitting as a solution.
We know from prior experience with splitting packages for large
arch-independent data that one of the more common mistakes that we'll make
is to move the wrong files: to put
Package: wnpp
Severity: wishlist
Owner: Timo Aaltonen
* Package name: 389-dsgw
Version : 1.1.9
Upstream Author : Red Hat, Inc.
* URL : http://directory.fedoraproject.org
* License : GPL-2, LGPL-2.1, MPL-1.1
Programming Lang: C
Description : 389 Director
Hi,
I'm making changes to the evolution email client and I want to know if
there's an easy way to test the changes I am doing without installing
the generated .debs.
Thanks!
--
David
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? C
Package: wnpp
Owner: Samuel Bronson
Severity: wishlist
* Package name: tack
Version : 1.07
Upstream Author : Thomas Dickey
* URL or Web page : ftp://ftp.invisible-island.net/ncurses/
* License : GPL-2+
Description : terminfo action checker
The 'tack' program is a d
Package: wnpp
Severity: wishlist
Owner: Rajmund Zawislak
* Package name: php-mongo
Version : 1.2.7
Upstream Author : Kristina Chodorow, Derick Rethans
* URL : http://pecl.php.net/package/mongo
* License : Apache License
Programming Lang: C
Description :
For some value of easy... I think most people who work with Debian packages
on a regular basis use a chroot environment to build and install packages.
Several similar programs can be used for this: pbuilder (and the faster
copy-on-write variant, cowbuilder) and sbuild are the ones I've used in the
* David Kalnischkies [2012-02-16 03:59 +0100]:
> On Thu, Feb 16, 2012 at 00:39, Russ Allbery wrote:
> >>> it needs to find and remove foo:*
foo:all (or foo:any) instead of foo:* would save the need to quote it.
> > Actually, why would that be the behavior? Why would dpkg --purge foo not
> > j
* Russ Allbery [2012-02-16 10:43 -0800]:
> * Users who want to co-install separate architectures will immediately
> encounter a dpkg error saying that the files aren't consistent. This
> means they won't be able to co-install the packages, but dpkg will
> prevent any actual harm from happeni
Carsten Hey writes:
> * Russ Allbery [2012-02-16 10:43 -0800]:
>> * Users who want to co-install separate architectures will immediately
>> encounter a dpkg error saying that the files aren't consistent. This
>> means they won't be able to co-install the packages, but dpkg will
>> prevent
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: 409 (new: 6)
Total number of packages offered up for adoption: 142 (new: 0)
Total number of packages request
On Thu, Feb 16, 2012 at 7:59 PM, Piotr Ożarowski wrote:
> Please don't. There are developers (like me) who prefer source package
> names to be as close as possible to upstream's name.
As a pedantic/info level warning, you are of course free to ignore it.
--
bye,
pabs
http://wiki.debian.org/Pau
Package: lintian
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
Dear Lintian maintainers,
The correspondance between source and binary package names has been discussed
on the debian-devel mailing list recently.
http://lists.debian.org/debian-devel/2012/02/msg00622.html
In part
28 matches
Mail list logo
