Hi,
Did you get time to look into issue?
Kindly please suggest the way forward to resolve it.
Thanks in advance.
Regards,
Preeti
On Tue, Feb 25, 2014 at 12:09 AM, Priti wrote:
> Hi,
> I read the blog regarding libpoco build failed . Link is
> https://lists.debian.org/debian-mentors/2007/01/msg
Hi,
I read the blog regarding libpoco build failed . Link is
https://lists.debian.org/debian-mentors/2007/01/msg00207.html
I am also facing same problem , which I debug and came to know that in case of
libpoco build if in its path any sub directory contain the pattern *.o* pattern
then build wi
Hi,
I read the blog regarding libpoco build failed . Link is
https://lists.debian.org/debian-mentors/2007/01/msg00207.html
I am also facing same problem , which I debug and came to know that in case of
libpoco build ,if in its path any sub directory contain the pattern *.o*
pattern then build w
Hi,
I read the blog regarding libpoco build failed . Link is
https://lists.debian.org/debian-mentors/2007/01/msg00207.html
I am also facing same problem , which I debug and came to know that in case of
libpoco build if in its path any sub directory contain the pattern *.o* pattern
then build wi
Dear mentors,
I am looking for a sponsor for the new version 1.3.6p2-1
of my package "poco".
It builds these binary packages:
libpoco-dev - Development files for POCO - The C++ Portable Components
libpococrypto9 - The C++ Portable Components Crypto library
libpococrypto9-dbg - The C++ Portable Co
Hi,
Hi Günter
can you please respond a short statement about API and ABI stability
of poco.
- Patrick
we generally try very hard to maintain API (source-code level)
compatibility between releases, especially in the core libraries
(Foundation, XML, Util, Net).
ABI (binary) compatibil
Patrick Roland Gansterer writes:
> George Danchev:
> > > I also uploaded a new upstream version 1.3.6p1.
> >
> > Uploaded with the last two changelog entries of yours included.
>
> Can you please upload poco-doc too. Thanks!
Sure, thanks for the poke. Uploaded with the following change: I moved y
George Danchev:
> > I also uploaded a new upstream version 1.3.6p1.
>
> Uploaded with the last two changelog entries of yours included.
>
Can you please upload poco-doc too. Thanks!
- Patrick
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe".
Hi Günter
can you please respond a short statement about API and ABI stability of poco.
- Patrick
-- Weitergeleitete Nachricht --
Betreff: Re: RFS: poco (updated package)
Datum: Samstag 26 Dezember 2009
Von: George Danchev
An: Patrick Roland Gansterer
Patrick Roland
Patrick Roland Gansterer writes:
> George Danchev:
> > I'm still waiting for an answer to this:
> > http://lists.debian.org/debian-mentors/2009/12/msg00300.html
>
> Do you think that a symbols file will be the correct solution? I didn't
> check the ABI history of poco, so i don't know if it is ba
2009/12/24 George Danchev :
> [...] Is the original
> maintainer (CC'ed) aware of you being a co-maintainer?
Yes, I am. We will maintain poco at alioth [1].
[1] http://git.debian.org/?p=collab-maint/poco.git
Regards,
--
Krzysztof Burghardt
http://www.burghardt.pl/
--
To UNSUBSCRIBE, email t
George Danchev:
> I'm still waiting for an answer to this:
> http://lists.debian.org/debian-mentors/2009/12/msg00300.html
Do you think that a symbols file will be the correct solution? I didn't check
the ABI history of poco, so i don't know if it is backward compatible and if
this is a goal of up
Patrick Roland Gansterer writes:
> Dear mentors,
Hi,
I'm still waiting for an answer to this:
http://lists.debian.org/debian-mentors/2009/12/msg00300.html
> I am looking for a sponsor for the new version 1.3.6-1
> of package "poco" and "poco-doc".
>
> It builds these binary packages:
> libpoco-
Patrick Roland Gansterer writes:
> Dear mentors,
Hi,
(I'm the usual sponsor of poco and poco-doc, and I'm looking for co-
sponsors;-)
Some preliminary comments follow:
> I am looking for a sponsor for the new version 1.3.6-1
> of package "poco" and "poco-doc".
>
> It builds these binary packag
Dear mentors,
I am looking for a sponsor for the new version 1.3.6-1
of package "poco" and "poco-doc".
It builds these binary packages:
libpoco-dev - Development files for POCO - The C++ Portable Components
libpococrypto9 - The C++ Portable Components Crypto library
libpococrypto9-dbg - The C++ P
> 2009/9/1 George Danchev :
> > This is now uploaded. No need to CC me, I'm subscribed. Thanks.
>
> Thank you! Would you upload poco-doc too?
> http://mentors.debian.net/debian/pool/main/p/poco-doc/poco-doc_1.3.5-1.dsc
Also uploaded. Thanks for the heads-up!
--
pub 4096R/0E4BD0AB
signature.a
2009/9/1 George Danchev :
> This is now uploaded. No need to CC me, I'm subscribed. Thanks.
Thank you! Would you upload poco-doc too?
http://mentors.debian.net/debian/pool/main/p/poco-doc/poco-doc_1.3.5-1.dsc
Best regards,
--
Krzysztof Burghardt
http://www.burghardt.pl/
--
To UNSUBSCRIBE, em
On Sunday 30 August 2009 20:37:13 Krzysztof Burghardt wrote:
> 2009/8/30 George Danchev :
> > * it would be better to explicitly build-depends on zlib1g-dev
>
> Dependency add and new package uploaded to mentors.d.n.
This is now uploaded. No need to CC me, I'm subscribed. Thanks.
--
pub 4096R/0E
2009/8/30 George Danchev :
> * it would be better to explicitly build-depends on zlib1g-dev
Dependency add and new package uploaded to mentors.d.n.
Regards,
--
Krzysztof Burghardt
http://www.burghardt.pl/
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "
On Sunday 30 August 2009 16:41:26 Krzysztof Burghardt wrote:
> 2009/5/27 George Danchev :
> > The only thing I'm not happy with is the staticaly linked zlib with
> > libpocofoundaton shared object and its debug variant. Can we please fix
> > that to dynamically link with the system provided libz, o
2009/5/27 George Danchev :
> The only thing I'm not happy with is the staticaly linked zlib with
> libpocofoundaton shared object and its debug variant. Can we please fix that
> to dynamically link with the system provided libz, or is there any reason I'm
> not aware of to use the zlib version prov
On Mon, Jun 1, 2009 at 3:38 PM, Dmitrijs Ledkovs
wrote:
> I'm not a Debian Developer but I've met this one with one of my
> "upstreams" as well. The reasoning is very vague. My upstream has been
> keeping an ancient copy of zlib in their tree/releases just because
> it's *easier* for them to buil
On Mon, Jun 1, 2009 at 5:38 PM, Dmitrijs Ledkovs
wrote:
> 2009/6/1 Krzysztof Burghardt :
>> 2009/5/31 Krzysztof Burghardt :
>>> 2009/5/27 George Danchev :
The only thing I'm not happy with is the staticaly linked zlib with
libpocofoundaton shared object and its debug variant. Can we plea
2009/6/1 Krzysztof Burghardt :
> 2009/5/31 Krzysztof Burghardt :
>> 2009/5/27 George Danchev :
>>> The only thing I'm not happy with is the staticaly linked zlib with
>>> libpocofoundaton shared object and its debug variant. Can we please fix that
>>> to dynamically link with the system provided li
2009/5/31 Krzysztof Burghardt :
> 2009/5/27 George Danchev :
>> The only thing I'm not happy with is the staticaly linked zlib with
>> libpocofoundaton shared object and its debug variant. Can we please fix that
>> to dynamically link with the system provided libz, or is there any reason I'm
>> not
2009/5/27 George Danchev :
> The only thing I'm not happy with is the staticaly linked zlib with
> libpocofoundaton shared object and its debug variant. Can we please fix that
> to dynamically link with the system provided libz, or is there any reason I'm
> not aware of to use the zlib version prov
Dear mentors,
I am looking for a sponsor for the new version 1.3.5-1
of my packages "poco" and "poco-doc".
It builds these binary packages:
libpoco-dev - Development files for POCO - The C++ Portable Components
libpococrypto8 - The C++ Portable Components Crypto library
libpococrypto8-dbg - The C
On Sunday 24 May 2009 21:14:10 krzysz...@burghardt.pl wrote:
> Dear mentors,
Hi,
> http://mentors.debian.net/debian/pool/main/p/poco/poco_1.3.5-1.dsc
Looks good. I also checked buildability of clamfs with poco 1.3.5-1 (the only
package in the archive which build-depends on libpobo-dev).
The o
Dear mentors,
I am looking for a sponsor for the new version 1.3.5-1
of my package "poco".
It builds these binary packages:
libpoco-dev - Development files for POCO - The C++ Portable Components
libpococrypto8 - The C++ Portable Components Crypto library
libpococrypto8-dbg - The C++ Portable Com
On Saturday 15 November 2008 13:16:07 Krzysztof Burghardt wrote:
> Dear mentors,
>
> I am looking for a sponsor for the new version 1.3.3p1-2
> of my package "poco".
Package uploaded. Thanks for taking care of these bugs.
--
pub 4096R/0E4BD0AB 2003-03-18
signature.asc
Description: This is a d
Dear mentors,
I am looking for a sponsor for the new version 1.3.3p1-2
of my package "poco".
It builds these binary packages:
libpoco-dev - Development files for POCO - The C++ Portable Components
libpococrypto6 - The C++ Portable Components Crypto library
libpococrypto6-dbg - The C++ Portable Co
On Thursday 30 October 2008 11:33:53 Krzysztof Burghardt wrote:
> Dear mentors,
Hi,
> I am looking for a sponsor for the new version 1.3.3p1-1
> of my package "poco".
...
> Also I am looking for a sponsor for the new version 1.3.3-1
> of my package "poco-doc".
Both uploaded. Thanks for your work
Dear mentors,
I am looking for a sponsor for the new version 1.3.3p1-1
of my package "poco".
It builds these binary packages:
libpoco-dev - Development files for POCO - The C++ Portable Components
libpococrypto6 - The C++ Portable Components Crypto library
libpococrypto6-dbg - The C++ Portable Co
On Friday 27 June 2008, George Danchev wrote:
> On Thursday 26 June 2008, Krzysztof Burghardt wrote:
--cut--
> > I just realized that I forgot to add new patch to patches/00list, so
> > pacakge is still buggy. Version 1.3.2+dfsg1-3 has this missing line
> > add.
> >
> > http://mentors.debian.net/de
On Thursday 26 June 2008, Krzysztof Burghardt wrote:
> Hello George,
>
> 2008/6/25 George Danchev <[EMAIL PROTECTED]>:
> > On Wednesday 25 June 2008, Krzysztof Burghardt wrote:
> >> I am looking for a sponsor for the new version 1.3.2+dfsg1-2
> >> of my package "poco".
>
> [...]
>
> >> The upload w
Hello George,
2008/6/25 George Danchev <[EMAIL PROTECTED]>:
> On Wednesday 25 June 2008, Krzysztof Burghardt wrote:
>> I am looking for a sponsor for the new version 1.3.2+dfsg1-2
>> of my package "poco".
[...]
>> The upload would fix these bugs: 487392, 487394, 487934
>
>An excellent bug
On Wednesday 25 June 2008, Krzysztof Burghardt wrote:
> Dear mentors,
Hello,
> I am looking for a sponsor for the new version 1.3.2+dfsg1-2
> of my package "poco".
>
> It builds these binary packages:
> libpoco5-dev - Development files for POCO - The C++ Portable Components
> libpocodata5 - The C
Dear mentors,
I am looking for a sponsor for the new version 1.3.2+dfsg1-2
of my package "poco".
It builds these binary packages:
libpoco5-dev - Development files for POCO - The C++ Portable Components
libpocodata5 - The C++ Portable Components Data library
libpocodata5-dbg - The C++ Portable Com
George Danchev <[EMAIL PROTECTED]> writes:
> Ops, sorry bad row counting. I meant that
> $expected_name =~ s/([0-9])\.so\./$1-/; won't cope with well with name.so.1
It will indeed not match name.so.1 at all, which is intentional. :)
This implements the rule in library naming that says that a l
2008/6/9 George Danchev <[EMAIL PROTECTED]>:
> Uploaded. That will hang in NEW for a while. Thanks for your work and
> patience.
Thank you for sponsoring it!
Regards,
--
Krzysztof Burghardt <[EMAIL PROTECTED]>
http://www.burghardt.pl/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subje
On Monday 09 June 2008, Russ Allbery wrote:
> George Danchev <[EMAIL PROTECTED]> writes:
> > Actually it would be smarter do ship only the detached debugging symbols
> > I believe. I can't think of a use case where the debugging version of
> > the shared library would be desperately needed or prefe
George Danchev <[EMAIL PROTECTED]> writes:
> Actually it would be smarter do ship only the detached debugging symbols
> I believe. I can't think of a use case where the debugging version of
> the shared library would be desperately needed or preferred, or I'm
> wrong ?
Well, usually the reason wh
On Monday 09 June 2008, Krzysztof Burghardt wrote:
> 2008/6/8 George Danchev <[EMAIL PROTECTED]>:
> > So I believe that the version 1.3.2+dfsg1-1 you have uploaded to mentors
> > on 07-Jun-2008 22:00 (ah I hate dealing with rewritten changelog
> > history;-) is basically ok, except that lintian ove
On Monday 09 June 2008, Russ Allbery wrote:
> George Danchev <[EMAIL PROTECTED]> writes:
> > shared library goes in /usr/lib and as expected lintian complains with:
> > libpocoxml5-dbg: package-name-doesnt-match-sonames libPocoXMLd5
> > because of the missing 'd' before '5', at least, hence that le
George Danchev <[EMAIL PROTECTED]> writes:
> shared library goes in /usr/lib and as expected lintian complains with:
> libpocoxml5-dbg: package-name-doesnt-match-sonames libPocoXMLd5
> because of the missing 'd' before '5', at least, hence that leads us to a
> package name as `libpocoxmld5-dbg',
2008/6/8 George Danchev <[EMAIL PROTECTED]>:
> So I believe that the version 1.3.2+dfsg1-1 you have uploaded to mentors on
> 07-Jun-2008 22:00 (ah I hate dealing with rewritten changelog history;-) is
> basically ok, except that lintian override files should be installed for all
> these -dbg packag
On Sunday 08 June 2008, George Danchev wrote:
> On Saturday 07 June 2008, Krzysztof Burghardt wrote:
> > Hello George,
Hi Krzysztof,
--cut--
> So, as libpkg-guide suggests in table 5.1 (soname: libfoo.so.4 => pkgname:
> libfoo4) and lintian asks us to end in -dbg since we install
> in /usr/lib/de
On Sunday 08 June 2008, George Danchev wrote:
--cut--
> Yes, dh_strip -k was called to split debigging symbols in a separate file
> (containing the detached debugging symbols) in usr/lib/debug/, in order to
> avoid binary duplications with things we want debugable, but the above
> oneliner produces
On Sunday 08 June 2008, Russ Allbery wrote:
> George Danchev <[EMAIL PROTECTED]> writes:
> > On Saturday 07 June 2008, Krzysztof Burghardt wrote:
> >> This looks reasonable, but trigger another lintian warrning:
> >>
> >> N: Processing binary package libpocoxml5-dbg (version 1.3.2+dfsg1-1) ...
> >>
George Danchev <[EMAIL PROTECTED]> writes:
> On Saturday 07 June 2008, Krzysztof Burghardt wrote:
>> This looks reasonable, but trigger another lintian warrning:
>>
>> N: Processing binary package libpocoxml5-dbg (version 1.3.2+dfsg1-1) ...
>> W: libpocoxml5-dbg: package-name-doesnt-match-sonames
On Saturday 07 June 2008, Krzysztof Burghardt wrote:
> Hello George,
>
> 2008/6/7 George Danchev <[EMAIL PROTECTED]>:
> >As a user of that package, I'm still reluctant to ship it in a
> > shape where lintian is not happy enough. I've read your reasoning about
> > debug package names you hav
Hello George,
2008/6/7 George Danchev <[EMAIL PROTECTED]>:
>As a user of that package, I'm still reluctant to ship it in a shape
> where
> lintian is not happy enough. I've read your reasoning about debug package
> names you have choosen, but I still don't see a good reason not to have
>
On Saturday 07 June 2008, Krzysztof Burghardt wrote:
> 2008/6/6 Vincent Bernat <[EMAIL PROTECTED]>:
> > OoO En cette nuit nuageuse du vendredi 06 juin 2008, vers 00:26,
> >
> > "Krzysztof Burghardt" <[EMAIL PROTECTED]> disait:
> >> http://mentors.debian.net/debian/pool/main/p/poco/poco_1.3.
On Friday 06 June 2008, Vincent Bernat wrote:
> OoO En cette nuit nuageuse du vendredi 06 juin 2008, vers 00:26,
>
> "Krzysztof Burghardt" <[EMAIL PROTECTED]> disait:
> >> As Cyril stated in another post, you must (by policy) put this
> >> information in debian/copyright. Sorry
2008/6/6 Vincent Bernat <[EMAIL PROTECTED]>:
> OoO En cette nuit nuageuse du vendredi 06 juin 2008, vers 00:26,
> "Krzysztof Burghardt" <[EMAIL PROTECTED]> disait:
>> http://mentors.debian.net/debian/pool/main/p/poco/poco_1.3.2+dfsg1-1.dsc
>> http://mentors.debian.net/debian/pool/main/p/poc
OoO En cette nuit nuageuse du vendredi 06 juin 2008, vers 00:26,
"Krzysztof Burghardt" <[EMAIL PROTECTED]> disait:
>> As Cyril stated in another post, you must (by policy) put this
>> information in debian/copyright. Sorry to have hinted an outdated
>> information (some t
2008/6/4 Vincent Bernat <[EMAIL PROTECTED]>:
> As Cyril stated in another post, you must (by policy) put this
> information in debian/copyright. Sorry to have hinted an outdated
> information (some translations are not up-to-date, look at the english
> version of the policy).
Do
OoO En cette nuit nuageuse du mardi 03 juin 2008, vers 00:16, "Krzysztof
Burghardt" <[EMAIL PROTECTED]> disait:
> 2008/5/22 Vincent Bernat <[EMAIL PROTECTED]>:
>> I did not check if it is a requirement, but debug version of library are
>> usually suffixed by "-dbg". For example libpocoxml5-dbg.
On 02/06/2008, Krzysztof Burghardt wrote:
> > Since you are removing non-free stuff from orig tarball, you
> > should either explain in README.Debian-source how to get the dfsg
> > tarball from the orig tarball or add a get-orig-source in
> > debian/rules.
>
> README.Debian-source added. Cha
2008/5/22 Vincent Bernat <[EMAIL PROTECTED]>:
> I did not check if it is a requirement, but debug version of library are
> usually suffixed by "-dbg". For example libpocoxml5-dbg. Is there any
> difference between the debug and non debug versions apart from stripped
> symbols? If there is no
OoO En ce début d'après-midi ensoleillé du samedi 17 mai 2008, vers
15:51, "Krzysztof Burghardt" <[EMAIL PROTECTED]> disait:
> It builds these binary packages:
> libpoco5-dev - Development files for POCO - The C++ Portable Components
> libpocodata5 - The C++ Portable Components Data library
>
Dear mentors,
I am looking for a sponsor for the new version 1.3.2+dfsg1-1
of my package "poco".
It builds these binary packages:
libpoco5-dev - Development files for POCO - The C++ Portable Components
libpocodata5 - The C++ Portable Components Data library
libpocodatad5 - The C++ Portable Compon
Dear mentors,
I am looking for a sponsor for the new version 1.3.2+dfsg1-1
of my package "poco".
It builds these binary packages:
libpoco5-dev - Development files for POCO - The C++ Portable Components
libpocodata5 - The C++ Portable Components Data library
libpocodatad5 - The C++ Portable Compon
Dear mentors,
I am looking for a sponsor for the new version 1.3.2+dfsg1-1
of my package "poco".
It builds these binary packages:
libpoco5-dev - Development files for POCO - The C++ Portable Components
libpocodata5 - The C++ Portable Components Data library
libpocodatad5 - The C++ Portable Compon
2008/1/20, Russ Allbery <[EMAIL PROTECTED]>:
> I believe that you should either license your packaging work under the
> same license as the upstream source or add an exception to the licensing
> on your packaging work to allow it to be linked with OpenSSL.
I think simple patches are not eligible f
"Krzysztof Burghardt" <[EMAIL PROTECTED]> writes:
> 2008/1/19, Aníbal Monsalve Salazar <[EMAIL PROTECTED]>:
>> On Sat, Jan 19, 2008 at 09:38:39AM +0100, Krzysztof Burghardt wrote:
>> >The package appears to be lintian clean.
>>
>> lintian -i --show-overrides poco_1.2.9-3_i386.changes
>> W: libpoco2
On Sat, Jan 19, 2008 at 09:38:39AM +0100, Krzysztof Burghardt wrote:
>The package appears to be lintian clean.
lintian -i --show-overrides poco_1.2.9-3_i386.changes
W: libpoco2: possible-gpl-code-linked-with-openssl
N:
N: This package appears to be covered by the GNU GPL but depends on the
N:
2008/1/19, Aníbal Monsalve Salazar <[EMAIL PROTECTED]>:
> On Sat, Jan 19, 2008 at 09:38:39AM +0100, Krzysztof Burghardt wrote:
> >The package appears to be lintian clean.
>
> lintian -i --show-overrides poco_1.2.9-3_i386.changes
> W: libpoco2: possible-gpl-code-linked-with-openssl
> N:
> N: This
Dear mentors,
I am looking for a sponsor for the new version 1.2.9-3
of my package "poco".
It builds these binary packages:
libpoco-dev - Development files for POCO - The C++ Portable Components
libpoco2 - POCO - The C++ Portable Components
The package appears to be lintian clean.
The upload
Dear mentors,
I am looking for a sponsor for the new version 1.2.9-3
of my package "poco".
It builds these binary packages:
libpoco-dev - Development files for POCO - The C++ Portable Components
libpoco2 - POCO - The C++ Portable Components
The package appears to be lintian clean.
The upload
Dear mentors,
I am looking for a sponsor for the new version 1.2.9-3
of my package "poco".
It builds these binary packages:
libpoco-dev - Development files for POCO - The C++ Portable Components
libpoco2 - POCO - The C++ Portable Components
The package appears to be lintian clean.
The upload
Dear mentors,
I am looking for a sponsor for the new version 1.2.9-3
of my package "poco".
It builds these binary packages:
libpoco-dev - Development files for POCO - The C++ Portable Components
libpoco2 - POCO - The C++ Portable Components
The package appears to be lintian clean.
The upload
Daniel Baumann wrote:
> good so far. as it's late already (00:28 localtime). i'll will do an
> intensive check tomorrow to make sure we didn't miss any file/license.
What about this license check?
I have uploaded a bit updated version of poco.
(poco-ssl and poco-doc are new)
http://mentors.debia
Daniel Baumann wrote:
> Krzysztof Burghardt wrote:
> > Updated once again. I have listed all copyright holders.
> btw, i didn't found GPL code in the package, so, binaries of the non-ssl
> sources are properly distributable.
> > Will copyright holders claim that I infringe on their rights?
> we as
Krzysztof Burghardt wrote:
> Updated once again. I have listed all copyright holders.
good so far. as it's late already (00:28 localtime). i'll will do an
intensive check tomorrow to make sure we didn't miss any file/license.
btw, i didn't found GPL code in the package, so, binaries of the non-ss
On (13/01/07 22:12), Krzysztof Burghardt wrote:
> Daniel Baumann wrote:
> > btw, just curious: are there any reasons to not use the -ssl tarball
> > from upstream?
>
> This problem is known as "OpenSSL and GPL software". What happen if
> there is a GPL software (and I'm not copyright holder). I e
On Sat, 2007-01-13 at 22:12 +0100, Krzysztof Burghardt wrote:
> > and, are you going to package the docs (assumed they are
> > redistributable, i didn't check for that)?
>
> Yes, but if it is another upstream tarball should I make another source
> package?
Yes, that's right.
Thijs
signature.a
Daniel Baumann wrote:
> ok, now everything is fine except the copyright file.
Updated once again. I have listed all copyright holders.
Virtually every file in this library have different licence: BOOST,
4-BSD, 3-BSD and others. Even one copyright holder have files on more
then one license. Do I
Krzysztof Burghardt wrote:
> Fixed and uploaded.
ok, now everything is fine except the copyright file.
some files belongs to different copyright holders than the main upstream
author, and are under a different license. you need to list them all,
look at tinyerp-client for an example for a multi-l
Daniel Baumann wrote:
> use the one supplied by upstream (which doesn't unpack to poco-1.2.8.orig).
Fixed and uploaded.
--
Krzysztof Burghardt <[EMAIL PROTECTED]>
http://www.burghardt.pl/
signature.asc
Description: To jest część listu podpisana cyfrowo
Krzysztof Burghardt wrote:
> Indeed, but for unknown reason only if build from "poco-1.2.8.orig"
> directory. Build using pbuilder and from "poco-1.2.8" works for me.
well, you've rebuild the orig.tar.gz for unknown reason anyway, please
use the one supplied by upstream (which doesn't unpack to po
Daniel Baumann wrote:
> * the package does not build:
(...)
> make[2]: Leaving directory `/home/user/poco-1.2.8.orig/XML'
Indeed, but for unknown reason only if build from "poco-1.2.8.orig"
directory. Build using pbuilder and from "poco-1.2.8" works for me.
> if you fixed above things, i'll che
Krzysztof Burghardt wrote:
> http://mentors.debian.net/debian/pool/main/p/poco/poco_1.2.8-1.dsc
* remove the useless empty line at the end of changelog.
* can you reword the long description to something more easy and
shorter?
* docs is a non prefixed helper, please prefix it with the
Dear mentors,
I am looking for a sponsor for my package "poco".
* Package name: poco
Version : 1.2.8-1
Upstream Author : Applied Informatics Software Engineering GmbH and
Contributors
* URL : http://poco.sourceforge.net/
* License : Boost Software License
Sec
84 matches
Mail list logo
