Package: wnpp
Severity: wishlist
Owner: Peter Eisentraut
* Package name: cmark
Version : 0.26.1
Upstream Author : John MacFarlane
* URL : https://github.com/jgm/cmark
* License : BSD, MIT
Programming Lang: C
Description : CommonMark parsing and
On fre, 2012-06-15 at 09:39 -0400, Theodore Ts'o wrote:
> I'm trying to understand a better way of using the Origin: field as
> specified by DEP-3.
>
> I'm currently using something like this:
>
> Origin:
> http://git.kernel.org/?p=fs/ext2/e2fsprogs.git;a=commitdiff;h=8f00911a21
> f4e95de84c60e0
With recent dpkg(-source) changes, many packages are again failing to
build twice in a row, because of uncommitted upstream changes. Fixing
this was a lenny release goal, maybe it should be one again?!? Most
importantly, maybe someone who has access to one of those build grids
can run the old tes
Package: wnpp
Severity: wishlist
Owner: Peter Eisentraut
* Package name: check-postgres
Version : 2.14.3
Upstream Author : Greg Sabino Mullane
* URL : http://bucardo.org/wiki/Check_postgres
* License : BSD
Programming Lang: Perl
Description : script
I found out the hard way that when a package is built with
hardening-wrapper, then debugging it with gdb results in seriously
suboptimal backtraces like this:
#0 0xb7d01424 in __kernel_vsyscall ()
#1 0xb7816d11 in ?? ()
#2 0xb7e973a2 in ?? ()
#3 0xb7e9784b in ?? ()
#4 0xb7f1c8fd in ?? ()
#5
On Tue, 2009-09-29 at 13:36 +0900, Charles Plessy wrote:
> I know that there has already been much of talk about this, but I am am
> getting
> more and more uncomfortable removing .pl or .sh extensions from programs when
> upstream does not.
At least in cases where the programs/scripts could be c
On Tue, 2009-09-29 at 19:30 +1000, Ben Finney wrote:
> "Steve M. Robbins" writes:
>
> > I agree with Charles: this is unncessary, unproductive busy-work.
>
> The same characterisation could be given to other changes that raise the
> quality of software in Debian (e.g. ensuring that commands are
On Wednesday 05 August 2009 14:21:54 Cyril Brulebois wrote:
> Michael Banck (05/08/2009):
> > On Wed, Aug 05, 2009 at 10:15:22AM +0900, Charles Plessy wrote:
> > > And for the format of the patch, I do not know what to tell them
> > > apart that unified diff is the preferred format of some Debian
On Wednesday 24 June 2009 16:58:52 Gunnar Wolf wrote:
> Driving licenses are expressly not accepted as official ID documents
> in Mexico, even if they are government-issued.
That just begs the question: official to whom, and why? Ultimately, the
office clerk, the bar tender, or the key signer wi
On Tuesday 23 June 2009 08:22:17 Carsten Aulbert wrote:
> Hi,
>
> as suggested on debian-user I repost my question here (sorry for the
> cross post, but I think it's better than send to individual emails to
> both lists, feel free to remove the other list)
>
> I'm currently packaging some "internal
There is a bit of discussion in bug #487546 about whether using cc or gcc as
the compiler is appropriate.
Particular questions:
* Are Debian packages supposed to be built by default using /usr/bin/gcc (or
whatever gcc is first in the path)? Or is it valid to use cc?
* What interface is the "c
On Friday 15 May 2009 12:28:07 Riku Voipio wrote:
> a release goal is IMHO something that needs fixes in a sweep of
> packages in archive before release. This change OTOH just needs fixes
> to sbuild and then some infrastructure work (deploying new sbuild/buildd
> everywhere).
Per upstream, this w
On Wednesday 13 May 2009 21:55:00 Guillem Jover wrote:
> So, there's missing support in sbuild (#501230), which arguably is
> a pretty recent bug report, but AFAIR I sent a mail to Ryan long time
> ago when drafting the wildcard support and never heard back, but then
> I never insisted again, so th
Since etch, dpkg has supported architecture wildcards such as "linux-any" and
"any-powerpc", which can, among other things, be used to express Linux-only
build dependencies like this:
Build-Depends: libcap2-dev [linux-any]
instead of one of the previous approaches:
Build-Depends: libcap2-dev |
On Monday 11 May 2009 09:49:31 Raphael Hertzog wrote:
> On Mon, 11 May 2009, Peter Eisentraut wrote:
> > Well, debuild calls dpkg-buildpackage most of the time, unless you give a
> > specific target (which would again possibly be of interest to those who
> > are interested in
On Monday 11 May 2009 07:45:02 Manoj Srivastava wrote:
> Changing defaults with a large installed base begs the
> question: Why? Random churn for churns sake is not the answer.
But upgrades would (should?) keep exim installed. A new default would only
affect new installations.
--
To
On Monday 11 May 2009 00:06:09 Steve Langasek wrote:
> Or maybe I've misunderstood, and there are
> Debian developers who are building official packages for *upload* by
> calling debian/rules by hand, and that's what people are concerned about
> preserving while still getting the benefits of these
On Sunday 10 May 2009 13:56:04 Steve Langasek wrote:
> I thought it was generally recognized that it's a Bad Idea to implement
> config files using your interpreter's 'include' functionality, but that's
> basically what we have here.
Guillem pointed out one problem: Either you do it via a make inc
On Saturday 09 May 2009 00:58:56 Russ Allbery wrote:
> Wouldn't our users expect to get the documentation
> with many of these packages by default? Normally you do get some
> documentation with things, and I've always been surprised by, say, ntp
> not including any documentation without installing
On Saturday 09 May 2009 02:35:18 Micah Anderson wrote:
> Some people clearly want postfix as the default MTA in Debian (I do),
> and some people dont want the default to change from Exim. There are
> some people who want something else, but so far that something else has
> not be technically satisf
On Monday 04 May 2009 23:53:15 Manoj Srivastava wrote:
> On Mon, May 04 2009, Peter Eisentraut wrote:
> > Please be sure to use
> >
> > FOO = bar
> >
> > instead of ":=", unless you have determined that you really wanted ":=".
> > In most
On Monday 04 May 2009 08:35:18 Guillem Jover wrote:
I like this proposal. A small nit:
> ,-- /usr/share/dpkg/build-options.mk
> # distro defaults
> FOO := distro
Please be sure to use
FOO = bar
instead of ":=", unless you have determined that you really wanted ":=". In
most cases it won't m
On Tuesday 28 April 2009 05:11:26 Russ Allbery wrote:
> Noah Slater writes:
> > As far as I see it:
> >
> > * Debian has dropped the Reply-To header because it is "harmful" in
> > some way.
> >
> > * Debian has mandated that all replies must behave as if Reply-To
> > existed.
>
> If this w
On Saturday 25 April 2009 02:51:40 Bradley Smith wrote:
> In light of the recent outdated config.{sub,guess} discussion I have
> decided to generate a list[0] of packages that have these files from before
> June 2006, which is when the AVR32 architecture was added.
> The list was generated using l
As described in bug #514318 and elsewhere, the upstream NTP Project has
deprecated the ntpdate program a long time ago, and it may be time to drop it
from the Debian distribution.
Most of the functionality of ntpdate is now provided by ntpd (stepping the
clock without threshold, stepping the cl
Package: general
Severity: wishlist
With all the (helpful) email that a package maintainer gets nowadays, BTS,
PTS, Dak, DDPOMail robot, BTS link, etc., it becomes ever weirder to just
filter them into appropriate mail folders. To illustrate that, here are
procmail rules that I have assembled
Package: wnpp
Severity: wishlist
Owner: Peter Eisentraut <[EMAIL PROTECTED]>
* Package name: chkconfig
Version : 10.3-90
Upstream Author : Michael Schroeder <[EMAIL PROTECTED]>
* License : GPL
Programming Lang: Perl
Description : system tool to enabl
Package: wnpp
Severity: wishlist
Owner: Peter Eisentraut <[EMAIL PROTECTED]>
* Package name: semantik
Version : 0.6.4
Upstream Author : Thomas Nagy <[EMAIL PROTECTED]>
* URL : http://freehackers.org/~tnagy/semantik.html
* License : QPL
Program
Josselin Mouette wrote:
> You are completely wrong on this topic. If you don’t use dh_icons, the
> icons shipped in your package won’t be available even to the application
> itself.
I don't claim to know the technical details of this, but I don't have
update-icon-caches installed and I have never
Josselin Mouette wrote:
> Debian has always been about integration. Don’t you register your
> documentation with doc-base so that your application integrates with
> centralized documentation systems?
I'm glad you bring up this comparison, but this is different. If someone
neglects to do doc-base
Package: general
Severity: normal
For a while now some folks have been going around asking various package
maintainers to inject dh_icons and/or dh_desktop calls into the package build
rules. The basic argument appears to be that your package needs to do this so
that my desktop environment will w
It has been suggested in bug #411520 that cdbs should be set up so that
it preserves CFLAGS set in the environment. But I haven't found any
clear specification about how debian/rules, being a makefile, should
deal with environment variables.
The best I could find is Policy 10.1 which states th
I have seen some packages lately, most prominently apache2, that replace the
entire NEWS.Debian file when they have some news to report. That way, older
news are lost, and users who don't upgrade to every intermediate version
(say, those who upgrade only between stable releases) are left in the
The upgrade to the new egroupware upstream drops several applications such as
the trouble-ticket system and the forum (because they were unmaintained or
the functionality was picked up by something else). I'm not sure how to
arrange an upgrade to this new version. On the one hand, no one wants
Package: wnpp
Severity: normal
We could use a few more people to help with the ntp package. We have a
new mailing list and a subversion repository hosted under the pkg-ntp
project on alioth. There is a boatload of bugs to deal with, most of
which are not that hard but need someone with a little
There are a few dozen source packages in the archive that contain a file
called debian/rules.old. In many cases, this was apparently the backup
copy during a cdbs conversion or something similar that should have
been removed. If you appear below, please consider fixing this.
Guenter Geiger (D
What do you think about this request? It seems reasonable, but I think if
this should be supported, there ought to be a general policy (formal or
informal) on it because I think many other init scripts will suffer from
similar problems.
-- Forwarded message --
Subject: Bug#3
Has the tech-ctte decision regarding the output format of md5sum [0] been
withdrawn in some form? It seems to be back to the old format:
$ md5sum http://lists.debian.org/debian-ctte/2004/06/msg00032.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? C
Steve Langasek wrote:
> * Use Debian's libtool.
I took one affected package (kmldonkey) from your list, relibtoolized
it as described, and rebuilt it, which failed spectacularly. Then, I
took another one (rekall), relibtoolized it, rebuilt it, and that
failed with a strikingly similar pattern.
k
Package: wnpp
Severity: wishlist
Owner: Peter Eisentraut <[EMAIL PROTECTED]>
* Package name: ggz
Version : 0.0.12
Upstream Author : Josef Spillner <[EMAIL PROTECTED]>
* URL : http://www.ggzgamingzone.org/
* License : GPL
Description : libr
I have been in a discussion with a fellow developer about the exact
meaning of the "0-day NMU policy" that is currently in effect.
Questions:
1. Does the 0-day policy only apply to RC bugs or to all bugs?
2. Does the "0 day" apply to the delay after the upload or to the delay
between the subm
Debian currently ships two ODBC driver managers, unixODBC (source
package "unixodbc") and iODBC (source package "libiodbc2"). These
basically do the same thing. Every package that wants to provide
database access through ODBC has to pick at build time which driver
manager to use. That in tur
Package: wnpp
Severity: wishlist
Owner: Peter Eisentraut <[EMAIL PROTECTED]>
* Package name: apt-rpm
Version : 0.5.15cnc6
Upstream Author : Gustavo Niemeyer <[EMAIL PROTECTED]>
Alfredo K. Kojima <[EMAIL PROTECTED]>
ba
Chasecreek Systemhouse wrote:
> Its a Accounting/Ledger system from http://www.sql-ledger.org/ --
apt-get install sql-ledger
Bernd Eckenfels wrote:
> Perhaps we need a "read this before submitting bugs against my
> package" function in reportbugs :)
That already exists: /usr/share/bug/. "reportbug galeon" provides a
reasonable example run.
Wouter Verhelst wrote:
> Is there any other reason why we would still need to use automake's
> dependency tracking anyway?
I don't think so. You may want to use it while working on the package,
but it seems like a fine idea to turn it off when finalizing the
package.
martin f krafft wrote:
> What do you think of this proposal. Are there any string points
> *against* it?
I have written scripts that explicitly call xterm because other terminal
emulator programs under X (which I had preferred otherwise) couldn't
handle certain programs. So in those situations
Marc Haber wrote:
> Do we have infrastructure to handle different answers for the same
> question? Maybe I'd like to have a different dbadmin password on my
> postgresql database than on mysql?
This discussion is about having a common set of chunks of text available
somewhere for use in the debco
Philipp Matthias Hahn wrote:
> What is consideres best practice when a package uses a SQL database
> (mysql, postgresql) and needs to create its own catalog and/or
> tables?
I say, create the tables when the package starts for the first time. As
an analogy, programs using Berkeley-type databases
e ago, or were never even in there in the first place.
--
Peter Eisentraut [EMAIL PROTECTED]
50 matches
Mail list logo
