On Wed, May 25, 2011 at 10:39 PM, Andreas Tille wrote:
> I have not built the package - but packages with lintian *warnings* can
> be uploaded (and IMHO the rpath issue is only a warning, but I might be
> wrong). Could anybody post the output of "lintian -i" ?
i cannot update the svn today. So I
Am Donnerstag, 26. Mai 2011, 09:31:19 schrieb Mathieu Malaterre:
See below
> On Wed, May 25, 2011 at 10:39 PM, Andreas Tille wrote:
> > I have not built the package - but packages with lintian *warnings* can
> > be uploaded (and IMHO the rpath issue is only a warning, but I might be
> > wrong).
Am Donnerstag, 26. Mai 2011, 09:31:19 schrieb Mathieu Malaterre:
> On Wed, May 25, 2011 at 10:39 PM, Andreas Tille wrote:
> > I have not built the package - but packages with lintian *warnings* can
> > be uploaded (and IMHO the rpath issue is only a warning, but I might be
> > wrong). Could anybo
On Thu, May 26, 2011 at 9:49 AM, Sebastian Hilbert
wrote:
>> So in summary rpath is an Error.
>>
>
> Is this something upstream should take care of (which I have CCed) or is this
> a packaging issue ?
I asked upstream why they used rpath in the first place but never got
an answer ...
I have not d
Hi Mathieu,
On Thu, May 26, 2011 at 09:31:19AM +0200, Mathieu Malaterre wrote:
>
> i cannot update the svn today. So I'll post the output of lintian I
> got the last time I tried:
at least I can confirm that svn commits work in principle if you adapt
your .ssh/known_hosts to the new server key.
Le Thu, May 26, 2011 at 10:18:35AM +0200, Andreas Tille a écrit :
> Hi Mathieu,
>
> at least I can confirm that svn commits work in principle if you adapt
> your .ssh/known_hosts to the new server key. If it is no technical
> reason on your side which prevents you from commiting we might just
> w
Charles,
On Thu, May 26, 2011 at 10:27 AM, Charles Plessy wrote:
> Le Thu, May 26, 2011 at 10:18:35AM +0200, Andreas Tille a écrit :
>> Hi Mathieu,
>>
>> at least I can confirm that svn commits work in principle if you adapt
>> your .ssh/known_hosts to the new server key. If it is no technical
>
Hi,
On Thu, May 26, 2011 at 11:25:18AM +0200, Mathieu Malaterre wrote:
> Here is what I have (before & after removing the $HOME/.subversion):
As I said - you need to fix .ssh/known_hosts.
> $ svn co
> svn+ssh://malat-gu...@svn.debian.org/svn/debian-med/trunk/packages/dicom3tools
> svn: To bet
On Thu, May 26, 2011 at 11:40 AM, Andreas Tille wrote:
>
> ssh svn.debian.org
thanks that works now :)
I have not touched the package since r6811, so the rpath issue is
still there. Hopefully Carlos will be able to guide us.
Thanks
--
Mathieu
--
To UNSUBSCRIBE, email to debian-med-requ...@
Hello,
thank you all for your work on this.
On 05/26/2011 10:18 AM, Andreas Tille wrote:
>> W: ginkgocadx: postinst-has-useless-call-to-ldconfig
>> W: ginkgocadx: postrm-has-useless-call-to-ldconfig
> That's a usual warning in connection with the rpath issue.
>> E: ginkgocadx: binary-or-shlib-
Am Donnerstag, 26. Mai 2011, 14:06:33 schrieb Steffen Möller:
> > As I said I would just link against the Debian packaged sqlite.
>
> This is of course annoying. I'd ignore that, too, though.
> Just make it appear in experimental as soon as possible.
> The SQLite is shipping as a source with gink
On Thu, May 26, 2011 at 02:22:52PM +0200, Hilbert, Sebastian wrote:
> > > As I said I would just link against the Debian packaged sqlite.
> >
> > This is of course annoying. I'd ignore that, too, though.
> > Just make it appear in experimental as soon as possible.
> > The SQLite is shipping as a
On 05/26/2011 08:19 AM, Charles Plessy wrote:
Le Thu, May 26, 2011 at 08:08:20AM +0200, Alex Mestiashvili a écrit :
Would it be possible just to roll back to latest commit done by you
, and start over from that point with my changes and the new
upstream 1.0.2 ?
Yes, this is something
On Wed, 25 May 2011, Andreas Tille wrote:
Unfortunately I am not yet able to commit anything after the alioth
rework. There is still an error:
svn: Can't create directory '/svn/debian-med/db/transactions/6851-1.txn':
Read-only file system
Uhmm. :-(
Any location for http download might do fo
On Thu, 26 May 2011, Steffen Möller wrote:
E: ginkgocadx: binary-or-shlib-defines-rpath
usr/lib/ginkgocadx/Plugins/libvisualizator.so.2.4.1.1
/usr/lib/openmpi/lib
So this is really an issue.
But I think lintian is wrong here. The error should just be
overridden.
No, the rpath is really adde
Hi, all.
The openmpi dependency may be caused by ITK because a huge portion of it is
template based.
I'll review the "rpath problem explain" reference that Sebastian sent to us,
but we are too busy right now to deep in the problem.
[ For some notes about the issue, please read below the mail pa
Am Donnerstag, 26. Mai 2011, 09:31:19 schrieb Mathieu Malaterre:
response from upsteam (unquoted) see below.
start of response
Hi, all.
The openmpi dependency may be caused by ITK because a huge portion of it is
template based.
I'll review the "rpath problem explain" reference that Sebastian
On Thu, May 26, 2011 at 08:03:49PM +0200, Thorsten Alteholz wrote:
>
> Did you find anything?
What exactly is the problem / error message if you try to commit?
> As everybody else but me could commit something,
> maybe I lost the write access to the repository? So maybe it would help
> to add
Hi Alex,
I found that format-patch can be given a path, so that it only produces patch
for it. Here is how I have prepared a new cufflinks repository:
debcheckout -a git://git.debian.org/debian-med/cufflinks.git --git-track='*'
cd cufflinks/
git format-patch 0b7256275dc8b8f7495a46b6b337395
On 05/27/2011 07:56 AM, Charles Plessy wrote:
Hi Alex,
I found that format-patch can be given a path, so that it only produces patch
for it. Here is how I have prepared a new cufflinks repository:
debcheckout -a git://git.debian.org/debian-med/cufflinks.git --git-track='*'
cd cufflinks/
20 matches
Mail list logo