On Sat, Jun 9, 2018 at 2:05 AM, Diane Trout wrote:
> Using a screen shot is just to deal with our build from source rule and
> to avoid a privacy leak from loading a remote resource.
I believe that rule applies to all of Debian main, not just ELF binaries.
--
bye,
pabs
On Fri, 2018-06-08 at 10:05 +0800, Paul Wise wrote:
> On Fri, Jun 8, 2018 at 5:59 AM, Diane Trout wrote:
>
> > How do I replace the .orig.tar.gz that I already uploaded?
>
> You will need a new upstream version, typically people use
> 0.1.2+dfsg1
> (for DFSG issues) or 0.1.2+ds1 (for other
On Fri, Jun 8, 2018 at 5:59 AM, Diane Trout wrote:
> How do I replace the .orig.tar.gz that I already uploaded?
You will need a new upstream version, typically people use 0.1.2+dfsg1
(for DFSG issues) or 0.1.2+ds1 (for other repack reasons) in these
sort of situations.
> I was planning on
> > I would suggest talking to upstream about fixing this properly (no
> > prebuilt files or embedded code copies in the VCS and tarballs).
>
> And in the meantime repacking the existing tarball to remove the
> sourceless files.
>
I was suspecting that was going to be the answer...
How do I
On 06/06/2018 06:30 AM, Diane Trout wrote:
> Hi,
>
> I discovered a mistake I made with packaging dask.
>
> There's two static html files which embed some bokeh generated
> javascript plot code that's in dask 0.17.5 and I uploaded that to the
> Debian.
>
> There doesn't appear to be source to
On June 6, 2018 4:42:44 AM UTC, Paul Wise wrote:
>On Wed, Jun 6, 2018 at 12:30 PM, Diane Trout wrote:
>
>> I was planning on patching the references to the .html files out and
>> removing them in the debian/rules files.
>>
>> But is that enough?
>
>That doesn't fix the orig.tar.gz.
>
>I would
On Wed, Jun 6, 2018 at 12:30 PM, Diane Trout wrote:
> I was planning on patching the references to the .html files out and
> removing them in the debian/rules files.
>
> But is that enough?
That doesn't fix the orig.tar.gz.
I would suggest talking to upstream about fixing this properly (no
7 matches
Mail list logo
