❦ 4 janvier 2017 19:25 +0100, Sebastian Parschauer :
>>> Should I append the following lines to the new upstream release entry in
>>> debian/changelog?
>>>
>>>+ Closes #618464
>>>+ Closes #689057
>>>+ Closes #822604
>>>
>>> This should auto-close these bugs,
On 04.01.2017 14:55, Vincent Bernat wrote:
> ❦ 4 janvier 2017 12:08 +0100, Sebastian Parschauer :
>> Should I append the following lines to the new upstream release entry in
>> debian/changelog?
>>
>>+ Closes #618464
>>+ Closes #689057
>>+ Closes #822604
>>
>>
❦ 4 janvier 2017 12:08 +0100, Sebastian Parschauer :
>> Thanks, that hint was crucial. I've implemented all that and updated the
>> source branch. Should be ready for upload now.
>>
>> https://raw.githubusercontent.com/sriemer/scanmem-debian/source/scanmem_0.16-1.dsc
>
>
On 04.01.2017 10:33, Sebastian Parschauer wrote:
> Thanks, that hint was crucial. I've implemented all that and updated the
> source branch. Should be ready for upload now.
>
> https://raw.githubusercontent.com/sriemer/scanmem-debian/source/scanmem_0.16-1.dsc
Andrea Stacchiotti (in CC) reported
On 02.01.2017 22:55, Vincent Bernat wrote:
> OK. In debian/control, ${python:Depends} already expands to python (>=
> 2.7), so you don't need to put it a second time (but that's really
> nitpicking). Also, I just noticed that gameconqueror is "Architecture:
> any" while it should be "Architecture:
❦ 2 janvier 2017 21:49 +0100, Sebastian Parschauer :
> It is intended and requested upstream to provide a separate libscanmem
> so that further tools can be built against it. We'll have to rework the
> public API any ways in v0.17. So I've dropped the separate libscanmem
>
On 02.01.2017 12:04, Vincent Bernat wrote:
> ❦ 2 janvier 2017 11:10 +0100, Sebastian Parschauer :
>> See:
>> https://github.com/sriemer/scanmem-debian/blob/source/scanmem_0.16-1.dsc
>
> This is not very convenient since I cannot use dget on this URL. But, I
> have
❦ 2 janvier 2017 11:10 +0100, Sebastian Parschauer :
> On 02.01.2017 10:48, Vincent Bernat wrote:
>>> I don't know what else I should do. Please upload!
>>
>> Emilio may be currently busy. You have better chance of getting someone
>> else helping with the upload if you
On 02.01.2017 10:48, Vincent Bernat wrote:
>> I don't know what else I should do. Please upload!
>
> Emilio may be currently busy. You have better chance of getting someone
> else helping with the upload if you provide a link to a .dsc so that
> people don't have to look at where the original
❦ 2 janvier 2017 10:12 +0100, Sebastian Parschauer :
>> Please upload! TIA
>
> We are reaching the new package submission deadline for Debian Stretch
> 2017-01-05 very soon.
>
> More than 5 years old version 0.13 which is full of bugs and insecure
> will be in Stretch if
On 17.12.2016 20:18, Sebastian Parschauer wrote:
> Please upload! TIA
We are reaching the new package submission deadline for Debian Stretch
2017-01-05 very soon.
More than 5 years old version 0.13 which is full of bugs and insecure
will be in Stretch if nobody uploads my new package from:
Hi Emilio,
we haven't forgotten you. We've worked hard and we've released v0.16
with the requested changes.
See: https://github.com/scanmem/scanmem/releases/tag/v0.16
See: https://github.com/sriemer/scanmem-debian
Now I'm asking you to upload the package. TIA
On 01.06.2016 23:14, Emilio
On 02/06/16 08:50, Sebastian Parschauer wrote:
> Hi Emilio,
>
> no problem, we used the time to bring version 0.16 coming with ranges
> search as well as Android and openSUSE support on its way. We can
> release any time but it would be great if we could fix the window resize
> bug and the
Hi Emilio,
no problem, we used the time to bring version 0.16 coming with ranges
search as well as Android and openSUSE support on its way. We can
release any time but it would be great if we could fix the window resize
bug and the example in the scanmem man page before doing so.
We've cleaned
Hi Sebastian, sorry for the huge delay.
On 28/04/16 01:59, Sebastian Parschauer wrote:
> On 25.04.2016 17:58, Emilio Pozuelo Monfort wrote:
>>> My plan is to become the new Debian scanmem package maintainer and to
>>> provide latest versions myself.
>>>
>>> I already started with a packaging repo
On 25.04.2016 17:58, Emilio Pozuelo Monfort wrote:
>> My plan is to become the new Debian scanmem package maintainer and to
>> provide latest versions myself.
>>
>> I already started with a packaging repo at:
>> https://github.com/sriemer/scanmem-debian
>>
>> I need supporters for this plan.
Control: tags -1 upstream fixed-upstream pending
Hi Sebastian,
On 25/04/16 17:37, Sebastian Parschauer wrote:
> The whole PolicyKit/pkexec stuff is implemented already. We only
> recently fixed a bug in it.
Great!
> There is even an upstream bug for the bad situation on Debian/Ubuntu. It
> has
17 matches
Mail list logo