(Please CC me, I am not subscribed to debian-devel)
Debian Bug Tracking System a scris:
> If you wish to submit further information on this problem, please
> send it to 528...@bugs.debian.org, as before.
It might be of interest to many people reading debian-devel to know that
svn-buildpackage is
Russ Allbery schrieb:
> Malte Forkel writes:
>
>> After some more checking and thinking, I guess I know what's causing
>> my problems: Its me, probably! I assume the source.changes files are
>> created while I setup everything for building a package, e.g. by
>> dh_make calling dpkg-buildpackage -
On Fri, 15 May 2009 10:49:07 +0300
Eddy Petrișor wrote:
> (Please CC me, I am not subscribed to debian-devel)
>
> Debian Bug Tracking System a scris:
> > If you wish to submit further information on this problem, please
> > send it to 528...@bugs.debian.org, as before.
>
> It might be of intere
Neil Williams a scris:
> On Fri, 15 May 2009 10:49:07 +0300
> Eddy Petrișor wrote:
>
>> (Please CC me, I am not subscribed to debian-devel)
>>
>> Debian Bug Tracking System a scris:
>>> If you wish to submit further information on this problem, please
>>> send it to 528...@bugs.debian.org, as bef
On Thu, May 14, 2009 at 10:13:43AM +0300, Peter Eisentraut wrote:
> 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 wildc
On Fri, May 15, 2009 at 12:28:07PM +0300, Riku Voipio wrote:
> On Thu, May 14, 2009 at 10:13:43AM +0300, Peter Eisentraut wrote:
> > 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
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 Thu, May 07, 2009 at 09:25:59AM +0200, Luca Niccoli wrote:
> 2009/5/7 Brian May :
>> However, I very much dislike this Unix "feature" as it means mail can
>> accumulate on any {user,system} account on any computer and not get
>> noticed by the {user,system administrator}.
> Not getting mail fr
Hello,
I am trying to package a *binary* package. This is a commercial
software but for ease of installation I am simply repackaging it.
I am getting closer to my goal, one of the remaining issue is:
E: libactiviz: ldconfig-symlink-referencing-wrong-file
usr/lib/libvtktiff.so.5.4 -> ./libvtk
On Fri, May 15, 2009 at 5:38 PM, Mathieu Malaterre
wrote:
> Hello,
>
> I am trying to package a *binary* package. This is a commercial
> software but for ease of installation I am simply repackaging it.
>
> I am getting closer to my goal, one of the remaining issue is:
>
> E: libactiviz: ldconfi
tag 494714 + patch
thanks
On Mon, 11 Aug 2008, Bastian Blank wrote:
> dpkg-genchanges should fold lines in the output to a sane length. There
> is a package in the archive (linux-modules-extra-2.6) which produces a
> 25k long Binary line, which is cropped by gpg during signing.
I guess we should
Raphael Hertzog writes:
> CCing -policy, do we need to update policy to allow Binary: fields
> over multiple lines?
Yes. (But I certainly have no objections to doing so.)
> Currently it only says that the fields are comma-separated and
> space-separated. Does "space" include newlines like in t
Malte Forkel writes:
> Russ Allbery schrieb:
>> Malte Forkel writes:
>>> After some more checking and thinking, I guess I know what's causing
>>> my problems: Its me, probably! I assume the source.changes files are
>>> created while I setup everything for building a package, e.g. by
>>> dh_make
Russ Allbery (15/05/2009):
> Calling dpkg-buildpackage -S produces a superfluous _sources.changes
> file, so anything that uses that method to produce a source package
> for build would either need to remove it or would leave it lying
> around. pdebuild uses dpkg-buildpackage -S to generate a sou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
Am Sa den 22. Sep 2007 um 0:18 schrieb Zakrn:
> On Sat, 2007-09-22 at 01:14 +0200, Josselin Mouette wrote:
> > I'm not talking about the libpcre3 package, but of the file
> > in /lib/libpcre.so.3 which was not brought by a Debian package.
>
>
Cyril Brulebois writes:
> Russ Allbery (15/05/2009):
>> Calling dpkg-buildpackage -S produces a superfluous _sources.changes
>> file, so anything that uses that method to produce a source package
>> for build would either need to remove it or would leave it lying
>> around. pdebuild uses dpkg-b
On 2009-05-15, Russ Allbery wrote:
> Cyril Brulebois writes:
>> Russ Allbery (15/05/2009):
>>> Calling dpkg-buildpackage -S produces a superfluous _sources.changes
>>> file, so anything that uses that method to produce a source package
>>> for build would either need to remove it or would leave
Russ Allbery writes:
> Cyril Brulebois writes:
> > You call it superfluous. It's particularly helpful for source-only
> > uploads.
>
> Well, yes, it's superfluous for Debian, which doesn't support
> source-only uploads.
But not for hackers preparing packages for Debian, who want to present
tho
Ben Finney writes:
> Russ Allbery writes:
>> Cyril Brulebois writes:
>>> You call it superfluous. It's particularly helpful for source-only
>>> uploads.
>> Well, yes, it's superfluous for Debian, which doesn't support
>> source-only uploads.
> But not for hackers preparing packages for Debian
Russ Allbery (15/05/2009):
> So, y'all realize that pdebuild --buildresult .. by default breaks the
> *_source.changes file that it generates because it regenerates a
> source package as part of the regular build, right? How are you
> actually using that *_source.changes file? Always having pdeb
Russ Allbery writes:
> So, y'all realize that pdebuild --buildresult .. by default breaks the
> *_source.changes file that it generates because it regenerates a
> source package as part of the regular build, right?
I've no idea about what pdebuild does, I don't use it. I was addressing
only the
Hello list (I've put a couple of people in Bcc to try to get more
feedback),
I'm working on integrating a PAM module into nss-ldapd and am looking
for input on this. The PAM module was kindly provided by Howard Chu from
the OpenLDAP project but I'm still working on the server part.
(more info on
22 matches
Mail list logo
