> Can you reproduce the problem with:
> $ cat tango-9.3.3-rc2.tar | tar --delete > \
> tango-9.3.3-rc2-excluded.tar
> ?
here
:~/Debian/tango$ cat tango-9.3.3-rc2.tar | tar --delete
tango-9.3.3/lib/java/RestServer-1.14.jar > tango-9.3.3-rc2-excluded.tar
tar:
Felix Natter writes:
> hi PICCA,
>
> PICCA Frederic-Emmanuel
> writes:
>>> Please confirm that
>>> > LANG=C tar --delete $(tar tf tango-9.3.3-rc2.tar | grep
>>> "lib/java/R.*jar") < tango-9.3.3-rc2.tar > tango.tar
>>> is inspired by `mk-origtargz`.
>>
>> not at all, I found this in #869087,
hi PICCA,
PICCA Frederic-Emmanuel
writes:
>> Please confirm that
>> > LANG=C tar --delete $(tar tf tango-9.3.3-rc2.tar | grep "lib/java/R.*jar")
>> > < tango-9.3.3-rc2.tar > tango.tar
>> is inspired by `mk-origtargz`.
>
> not at all, I found this in #869087, which is a tar bug with --delete.
>
hello Geert,
Geert Stappers writes:
> On Sun, Aug 25, 2019 at 01:25:22PM +, PICCA Frederic-Emmanuel wrote:
>> I tryed to reproduce the issue like this
>>
>> LANG=C tar --delete $(tar tf tango-9.3.3-rc2.tar | grep "lib/java/R.*jar") <
>> tango-9.3.3-rc2.tar > tango.tar
>> tar:
> Please confirm that
> > LANG=C tar --delete $(tar tf tango-9.3.3-rc2.tar | grep "lib/java/R.*jar")
> > < tango-9.3.3-rc2.tar > tango.tar
> is inspired by `mk-origtargz`.
not at all, I found this in #869087, which is a tar bug with --delete.
It is not clear to me what is the cmd executed by
On Sun, Aug 25, 2019 at 01:25:22PM +, PICCA Frederic-Emmanuel wrote:
> I tryed to reproduce the issue like this
>
> LANG=C tar --delete $(tar tf tango-9.3.3-rc2.tar | grep "lib/java/R.*jar") <
> tango-9.3.3-rc2.tar > tango.tar
> tar: tango-9.3.3/lib/java/RestServer-1.14.jar: Not found in
I tryed to reproduce the issue like this
LANG=C tar --delete $(tar tf tango-9.3.3-rc2.tar | grep "lib/java/R.*jar") <
tango-9.3.3-rc2.tar > tango.tar
tar: tango-9.3.3/lib/java/RestServer-1.14.jar: Not found in archive
tar: Exiting with failure status due to previous errors
Is it the right way
> mk-origtargz just calls tar --delete < file > newfile and as you can
> easily check this indeed gives the same error message.
the listed files are the right files as extracted by tar from the upstream
tar.gz, so
this is an issue with tar ?
Is it possible to display the exact tar command line
On Sun, Aug 25, 2019 at 08:24:14AM +, PICCA Frederic-Emmanuel wrote:
> > > ... an error like "could not remove *.jar" ...
> > Found jar deletion instruction
> > at
> > https://salsa.debian.org/science-team/tango/blob/master/debian/copyright#L5
>
> yes I use
> Files-Excluded: lib/java/*.jar
On Sun, Aug 25, 2019 at 08:01:52AM +, PICCA Frederic-Emmanuel wrote:
> > It cannot delete them because they are not there.
That was a wild guess. It seems the files are actually present.
> So their is a bug in mk-origtargz ?
>
> Who is in charge of the deletion ?
mk-origtargz just calls tar
looking at the directroy, I find this
drwxr-xr-x 11 picca picca 4096 août 20 17:23 tango-9.3.3
-rw-r--r-- 1 picca picca 282982400 août 25 08:37
tango_9.3.3~rc2+dfsg1.orig.tar
-rw-r--r-- 1 picca picca 232776497 août 25 08:36 tango-9.3.3-rc2.tar.gz
what is strange it that the extracted
Hello
> Found jar deletion instruction
> at https://salsa.debian.org/science-team/tango/blob/master/debian/copyright#L5
yes I use
Files-Excluded: lib/java/*.jar
from DEP-5 (it was find until now)
> I assume that upstream has stopped shipping jars in there .tar.gz
> If so, then it is a good
On Sun, Aug 25, 2019 at 12:58:58PM +0500, Andrey Rahmatullin wrote:
> On Sun, Aug 25, 2019 at 07:31:38AM +, PICCA Frederic-Emmanuel wrote:
> > Hello,
> >
> > When I try to import the new tango[1] sources with
> >
> > gbp import-orig -uscan
> >
> > I get this error
> >
> >
On Sun, Aug 25, 2019 at 07:31:38AM +, PICCA Frederic-Emmanuel wrote:
> Hello,
>
> When I try to import the new tango[1] sources with
>
> gbp import-orig -uscan
>
> I get this error
>
> :~/Debian/tango/tango$ LANG=C gbp import-orig --uscan
> gbp:info: Launching uscan...
> tar:
Hello,
When I try to import the new tango[1] sources with
gbp import-orig -uscan
I get this error
:~/Debian/tango/tango$ LANG=C gbp import-orig --uscan
gbp:info: Launching uscan...
tar: tango-9.3.3/lib/java/RestServer-1.14.jar: Not found in archive
tar:
On Wed, 03 Aug 2011, Picca Frédéric-Emmanuel wrote:
What do your mean exactly by sorted ?
sorted using the 'sort' program ?
sorted like the un-mangled symbols ?
IIRC it's sorted alphabetically on the string that appears in the symbols
file (i.e. un-mangeld symbol in your case). The tags are
Le Thu, 4 Aug 2011 08:02:44 +0200,
Raphael Hertzog hert...@debian.org a écrit :
IIRC it's sorted alphabetically on the string that appears in the symbols
file (i.e. un-mangeld symbol in your case). The tags are ignored for the
sort.
ok In fact my symbols where alphabetically sorted using
On Mon, 01 Aug 2011, Michael Tautschnig wrote:
Indeed symbol ordering may vary, but also there is no reason for
dpkg-gensymbols
to guarantee a particular ordering.
Well, dpkg-gensymbols does sort the symbols files. Precisely so that
diff are meaningful. Otherwise they would be useless.
Code
Le Wed, 3 Aug 2011 08:26:05 +0200,
Raphael Hertzog hert...@debian.org a écrit :
On Mon, 01 Aug 2011, Michael Tautschnig wrote:
Indeed symbol ordering may vary, but also there is no reason for
dpkg-gensymbols
to guarantee a particular ordering.
Well, dpkg-gensymbols does sort the
Le Fri, 29 Jul 2011 12:09:05 +0100,
Michael Tautschnig m...@debian.org a écrit :
Hi again,
Le Fri, 29 Jul 2011 09:45:53 +0100,
Michael Tautschnig m...@debian.org a écrit :
- Use the c++ tag to move to human-readable symbols and get rid of
problems due
to different name
Le Mon, 1 Aug 2011 10:35:53 +0200,
Niels Thykier ni...@thykier.net a écrit :
Hi,
Looks like you have architecture (or endian) specific symbols. You
probably have to make architecture specific symbols files in this case.
In case you would like to see an example I know of [1], which uses a
Hi,
[...]
Yes that is why I try to apply the generated patch and it does not work for
exemple
this hunk took from the armel architecture
[...]
as you can see the patch generated by dpkg-gensymbols can not apply.
Indeed symbols are not ordered the same way ??? Maybe this is due to the
* Michael Tautschnig m...@debian.org [110801 11:15]:
Indeed symbol ordering may vary, but also there is no reason for
dpkg-gensymbols
to guarantee a particular ordering. Although dpkg-gensymbols produces a diff,
this is surely not meant for you to apply directly as a patch: each change
Hello
I just added the symbol files to one of my packages [1], which provided two C++
libraries.
I solved by hand the build failure for the first on (liblog4tango4).
I would like your opinion about my fix [2]. I am not sure that I did the right
things.
Is seems that a few of the missing
Hi Frédéric,
I just added the symbol files to one of my packages [1], which provided two
C++ libraries.
I solved by hand the build failure for the first on (liblog4tango4).
I would like your opinion about my fix [2]. I am not sure that I did the
right things.
Is seems that a few of the
Le Fri, 29 Jul 2011 09:45:53 +0100,
Michael Tautschnig m...@debian.org a écrit :
- Use the c++ tag to move to human-readable symbols and get rid of problems
due
to different name mangling schemes.
yes it is nicer with c++ tag, is there an automatic way to convert a symbol
file to
this
On Fri, Jul 29, 2011 at 10:11:47AM +0200, Picca Frédéric-Emmanuel wrote:
It seems that my i386 package contain mmx instructions, is it allow ?
Sadly, no. It must work on a real 80486.
You may have an alternate code path for 80586 and higher, though, and choose
them at runtime.
On amd64 you
Hi again,
Le Fri, 29 Jul 2011 09:45:53 +0100,
Michael Tautschnig m...@debian.org a écrit :
- Use the c++ tag to move to human-readable symbols and get rid of problems
due
to different name mangling schemes.
yes it is nicer with c++ tag, is there an automatic way to convert a
Hi Picca (2011.07.29_10:11:47_+0200)
Is there a link somewhere explaining by examples how to deal with thoses
MISSING symbols
or differences of implementations ?
Is there a sort of concatenator script, which take all the build log and
generate a unique symbol file
with arch tags ?
It's
On Tue, 7 Aug 2007 14:25:13 +0200
PICCA Frédéric-Emmanuel [EMAIL PROTECTED]
wrote:
Dear mentors,
I am looking for a feedback on my tango package, it is not yet
finished but as it use a mysql database and this is my second
package, I asked here for critical views on it. It builds 2 libraries
On Tue, Aug 14, 2007 at 03:38:25PM +0200, picca wrote:
On Tue, 7 Aug 2007 14:25:13 +0200
PICCA Frédéric-Emmanuel [EMAIL PROTECTED]
wrote:
Dear mentors,
I am looking for a feedback on my tango package, it is not yet
finished but as it use a mysql database and this is my second
On Tue, 14 Aug 2007 09:48:21 -0400
Justin Pryzby [EMAIL PROTECTED] wrote:
u should support the general case where the SQL server is on a
remote host (not local).
Yes when writing the post I tell to miself but if I want to use a mysql
server on a remote host.
Do you have exemple of package
On Tue, Aug 14, 2007 at 05:54:38PM +0200, picca wrote:
On Tue, 14 Aug 2007 09:48:21 -0400
Justin Pryzby [EMAIL PROTECTED] wrote:
u should support the general case where the SQL server is on a
remote host (not local).
Yes when writing the post I tell to miself but if I want to use a
I guess dbconfig-common is the framework so apt-cache rdepends that.
Yes I am already using it in the package. but for now it install the databas on
the localhost.
I need a example of another package that deal with this remote host
installation.
Thank you
Frederic
Dear mentors,
I am looking for a feedback on my tango package, it is not yet finished but as
it use a mysql database and this is my second package, I asked here for
critical views on it.
It builds 2 libraries liblog4tango4 ans libtango5 and tango-db install the
tango-ds service.
Not much
35 matches
Mail list logo
