On (28/07/06 12:12), Manoj Srivastava wrote:
> On Fri, 28 Jul 2006 10:53:22 +0100, James Westby <[EMAIL PROTECTED]> said:
>
> > On (28/07/06 10:03), Lars Wirzenius wrote:
> >> pe, 2006-07-28 kello 00:03 +0100, James Westby kirjoitti:
> > But, yes, like all of
flict between pbuilder and dpkg-buildpackage?
>
I think I remember someone metioning this before, and it turned out to
be caused by something that seemed completely unrelated. Unfortuanately
I cannot remember what. Helpful eh?
James
--
James Westby --GPG Key ID: B577FE13-- h
On (17/08/06 00:57), Michael Rasmussen wrote:
>
> On 2006-08-17 00:53:16, James Westby wrote:
> >
> >You could see if chmod u+x configure in your debian/rules fixes it,
> >but
> >it shouldn't be necessary.
> >
> How I am going to do that? configure i
Package: wnpp
Severity: wishlist
Owner: James Westby <[EMAIL PROTECTED]>
* Package name: bazaar-webserve
Version : Unknown
Upstream Author : Goffredo Baroncelli
* URL : http://goffredo-baroncelli.homelinux.net/bazaar-dev/
* License : GPL
Programmin
package
by the same author, and he is great to work with.
I was wondering what the upload ettiquete should be. There is no now,
version, no bugs, and the packaging is fine. Do I try and find a sponsor
just for a change of maintainer, or do I wait until there is something
to do?
Let me know what you
s not supported (I'm not trying to trigger
that particular debate).
James
--
James Westby --GPG Key ID: B577FE13-- http://jameswestby.net/
seccure key - (3+)k7|M*edCX/.A:n*N!>|&7U.L#9E)Tu)T0>AM - secp256r1/nistp256
--
To UNSUBSCRIBE, email to [EMAIL PROTE
On (08/10/06 17:22), Uwe Hermann wrote:
> Hi,
>
> On Sat, Oct 07, 2006 at 10:36:25PM +0100, James Westby wrote:
> > If you have exim installed, you must either install postfix or write an
> > exim policy, as none currently exists.
> >
> > Is this still th
, so that it wont be
seen on installation, but if the user tries to reconfigure exim4 they
will be directed to the correct package.
James
--
James Westby --GPG Key ID: B577FE13-- http://jameswestby.net/
seccure key - (3+)k7|M*edCX/.A:n*N!>|&7U.L#9E)Tu)T0>AM - secp2
rypt, libtasn1, libksba
> (security-critical, some work required, having a team for these
> packages would be ideal)
I would like to be part of the team for these packages.
James
--
James Westby
[EMAIL PROTECTED]
http://jameswestby.net/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
w
ls as libcrypto as it is not meant to be a
drop in replacement, it is a whole different project. I don't think
there is a GPL compatible reimplementation of libcrypto, but maybe I'm
wrong.
Why do you require the same symbols? Have you already written the code
for libcrypto? If not what does it
the same gnutls libs.
Do you have a reference please? Is there a bug against gnutls?
You might like to contact [EMAIL PROTECTED] to
discuss these problems further, and for any help that I can provide you
with.
James
--
James Westby
[EMAIL PROTECTED]
http://jameswestby.net/
--
To
scribe to that mailing list, and get yourself added to the
alioth project and then coordinate your work with them.
James
--
James Westby
[EMAIL PROTECTED]
http://jameswestby.net/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
got a suggestion for a way to find the list of packages that
generate a certificate in their postinst? That would help the decision.
James
--
James Westby
[EMAIL PROTECTED]
http://jameswestby.net/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
; coordinate there. I've just filed #376047 too, so any bugs filed
> should be made to block that one.
>
I will help out where possible. I will hopefully email you later with
information on the packages that were referenced as [1] (snipped) that
might help you out as well.
James
--
James Westby
[EMAIL PROTECTED]
http://jameswestby.net/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
g.
While I'm out I'll be test building all the files with a .diff in the
failures dir. And tonight I might test build those in the success/used
dir for building without automake as I'm sure some of them don't need
it.
Good luck,
James
--
James Westby
[EMAIL PROTECTED]
http://jameswestby.net/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I am willing to work a bit on getting it in to shape, does anyone want
to volunteer to help out and then create patches for all the necessary
packages?
James
--
James Westby
[EMAIL PROTECTED]
http://jameswestby.net/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ging is currently native, and the insertion of the lib in to
the script will be removed, I just haven't done it yet.
Thanks,
James
--
James Westby
[EMAIL PROTECTED]
http://jameswestby.net/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On (28/07/06 10:03), Lars Wirzenius wrote:
> pe, 2006-07-28 kello 00:03 +0100, James Westby kirjoitti:
> > * Make it easier for package maintainers
> > - One extra dh_ call and maybe one more file in debian/
>
> How badly is this tied to debhelper? Any chance of desi
On (28/07/06 13:16), Lars Wirzenius wrote:
> pe, 2006-07-28 kello 10:53 +0100, James Westby kirjoitti:
> I don't like it when people make using helper packages de facto
> required. And debhelper isn't standard (meaning that you can expect
> everyone to use it), merely very c
On Mon, 2008-02-25 at 10:19 -0600, John Goerzen wrote:
> "Dirty history" is not only tolerated, but the *only* sane option with,
> lesse... rcs cvs svn darcs tla baz (bzr?)
bzr supports both ways of working, either cleaning up, or preserving
the history as is.
It has rebase support through a p
On Thu, 2008-06-05 at 10:56 +0200, Pierre Habouzit wrote:
> Bazaar currently suffers from #454313, but has reverse dependencies
> which prevent its sane removal from testing. It looks to me that bazaar
> is unmaintained upstream, the last 4 uploads in Debian are NMUs, and
> almost nobody is using i
On Tue, 2008-07-01 at 13:29 +0200, Josselin Mouette wrote:
> Le mardi 01 juillet 2008 à 11:55 +0100, James Westby a écrit :
> > Given that in runlevels 0 and 6 there is an init script that terminates
> > all running processes it is a waste to run an init script for each
> > pr
On Tue, 2008-07-01 at 14:42 +0200, Bernd Eckenfels wrote:
> In article <[EMAIL PROTECTED]> you wrote:
> > As I understand it, there is nothing magic about the approach taken, it
> > just doesn't install the symlinks for rc0.d and rc6.d, and expects that
> > the process will be cleaned up. It also r
On Tue, 2008-07-01 at 15:38 +0200, Frans Pop wrote:
> I happened to see a similar bug filed against backuppc.
>
> How many of these bugs have been filed?
> Are you aware of the Debian policy regarding mass bug filing [1]?
>
I have filed two (from memory). I am aware of that policy.
> IMO this i
Raphael Hertzog wrote:
> Hello,
>
> it looks like we quickly converged on something relatively well accepted.
> Current version: http://dep.debian.net/deps/dep3/
Thanks for working on this Raphael, I am glad to see it moving.
I have a few comments, but overall I like the current proposal. It is
gregor herrmann wrote:
> I agree that that's not completely obvious/intuitive for "newcomers"
> but consumers of the patch format (command line tools, web
> interfaces, ...) are free to expand them to URLs, and those
> interfaces are probably more used than the raw source packages by the
> people w
Guido Günther wrote:
>> I am concerned that just allowing to use git-format-patch will result in
>> people not making an effort to markup other metadata in DEP#3 format,
>> like bug numbers or reviewers and leave those as free-form in the body.
> We can have Forwarded:, Origin:, Received-by: in thi
Guido Günther wrote:
> Which isn't a problem on patch-queue branches since you either can
> recreate them anytime from what's in debian/patches or simply ammend the
> commit. They're supposed to be rebased frequently anyway.
"Supposed"?
That's not true in my opinion. It would tend to be hostile t
Jonathan Yu wrote:
> I'd like to see a feature to use cowbuilder's chroot instead, though I
> don't know of the technical challenges there. Certainly such a feature
> would make it easier to use and thus run more often.
That would be useful. It requires adding explicit support in piuparts
(with th
Ben Finney wrote:
> Ben Hutchings writes:
>
>> On Tue, 2009-08-18 at 22:36 +0300, Antti-Juhani Kaijanaho wrote:
>>> As I understand it, "A enhances B" has (more or less) the same
>>> effect as "B suggests A". Thus, the reverse Suggests relation would
>>> be redundant.
>> A plugin "enhances" the a
On Tue Dec 15 16:26:12 + 2009 Steffen Moeller wrote:
> Hello,
>
> I just received a request to upload a series of packages for Debian that
> are already available for Ubuntu.
>
> Is there a policy document on how to give appropriate credit for the
> original work? What if the version we are g
same. These handle most of this well. What I would like to do is come up
with a system like one of these, but specialised for Debian packaging,
so that the patches are stored under debian/patches, and the information
about them is stored in the vcs. However I can't come up with a design
that
On Mon, 2008-07-07 at 17:05 +0200, Frans Pop wrote:
> OK. I don't not remember that. A pointer to that discussion would be
> useful. You only included a link to a Ubuntu web page which is IMO not
> directly relevant when proposing structural changes in Debian (or at
> least: does not provide suf
On Mon, 2008-07-28 at 23:18 +1000, Ben Finney wrote:
> No, if the pages exist and other pages tend to treat them as
> interesting (i.e. interesting pages link to those pages), Google is
> working as advertised if it indexes and reports them.
On unactivated account pages launchpad now sets
so
e to attempt to answer my own questions.
On Mon, 2008-07-07 at 16:29 +0100, James Westby wrote:
> Therefore I'd like to ask a few questions:
>
> 1. Are there any objections to the approach that have not already
> been raised in the thread?
It doesn't appear so.
>
On Wed, 2008-07-30 at 14:58 +0800, Paul Wise wrote:
> If you don't yet have the full list of affected packages, providing
> the current list and saying it is incomplete and further bugs will be
> filed as daemons are audited should be fine.
Hi,
Below is the current list that I was able to calcula
On Tue, 2008-10-21 at 14:39 +0200, Lucas Nussbaum wrote:
> I'm not sure that filing lots of bugs about missing Depends on
> update-inetd really delays the release. Chris Lamb is fixing those bugs
> faster than I file them anyway ;)
You mean like this one?
http://bugs.debian.org/cgi-bin/bugrepor
On Mon, 2009-01-19 at 10:46 +0100, Olivier Berger wrote:
> There would be some need for inter-distro work here, maybe... any ideas
> on where to discuss that much welcome ;)
distributi...@lists.freedesktop.org would be a good place to start.
http://lists.freedesktop.org/mailman/listinfo/distribut
would be confused by this, in that they
wont know to unpack a source package that contains only a .diff.gz
against a .tar.gz of the appropriate version number.
Also, I guess you are opening up the possibility of creating a source
package containing both a .tar.gz and .diff.gz, which will also co
On (24/10/07 09:50), Bastian Blank wrote:
> > > 13 loop-aes305
>
> Deprecated by dm-crypt.
Not entirely true. However it is not going to go in to upstream, so the
effect is the same.
Thanks,
James
--
James Westby --GPG Key ID: B577FE13
On Wed, 31 Mar 2010 12:29:01 +1100, Ben Finney
wrote:
> Specifically, a behaviour of *recognising* that a package is in source
> format 1.0. That's a fact of that package in that state, that shouldn't
> change just because time has passed.
>
> In other words, a source package left as it was from
On Thu, 2009-03-05 at 22:19 +0100, Raphael Hertzog wrote:
> All in all, things are in a rather good shape but I still need some help.
> While I tested extensively the dpkg-source side, we still need to ensure
> that all our additional tools cope well with the new source package
> format (*-buildpac
On Sun, 2009-03-08 at 17:11 +0100, Raphael Hertzog wrote:
> There's nothing to specify here, dpkg-source uses all additional tarballs
> that match the regexp (exactly like it identifies the .orig tarball
> currently).
bzr-builddeb will endeavour to provide the ".orig.tar.gz" for a format 1
package
On Sun, 2009-03-08 at 16:07 +0100, Jan Hauke Rahm wrote:
> And how do you store that in a VCS if a second tarball includes files
> that actually overwrite files of the main orig tarball. At build time
> directories in the main orig tarball are supposed to be overwritten by
> the part tarball but if
On Mon, 2009-03-09 at 09:24 +0100, Raphael Hertzog wrote:
> If bzr-builddeb wants to provide the tarballs, they must have been
> injected at some point (otherwise you won't provide pristine tarballs)
> and you could record the additional information at that point.
That is almost true, except for
On Mon, 2009-03-09 at 12:30 +0100, Jan Hauke Rahm wrote:
> Imagine an orig tarball with a config directory and an orig part-tarball
> named orig-config.tar.whatever. The second tarball would overwrite
> what's in the config dir of the first one when executing dpkg-source -x.
> If you just store tha
On Wed, 2009-03-25 at 12:32 +0100, Romain Beauxis wrote:
> My personal experience is not consistent with this.
>
> I have several very small ocaml packages waiting in NEW for several weeks now.
> I am upstream on these packages, and, honnestly, it takes few minutes to
> check
> them (only 3 file
Package: wnpp
Severity: wishlist
Owner: James Westby
* Package name: lazr.uri (binary package python-lazr-uri)
Version : 1.0
Upstream Author : lazr developers: https://launchpad.net/~lazr-developers
* URL : https://launchpad.net/lazr.uri
* License : LGPL (3 or
On Mon, 2009-06-15 at 21:37 +0200, Joerg Jaspert wrote:
> On 11782 March 1977, Raphael Hertzog wrote:
>
> > This is a proposal to formalize a set of meta-information
> > to be embedded in patches applied to Debian packages. Most
> > patch systems allow for a free-from description preceeding
> > th
49 matches
Mail list logo
