Hello Dmitry, Gianfranco,
I did some research and testing into this bug...
On Sat, Apr 14 2018, kact...@gnu.org wrote:
> Hello. I am a bit lost about state of this RFS, but it seems I did
> stupid thing with format=1.0; complicating sponsoring.
>
> Let me settle things, provide sane package with
Hello,
On Sat, Apr 14 2018, kact...@gnu.org wrote:
> Hello. I am a bit lost about state of this RFS, but it seems I did
> stupid thing with format=1.0; complicating sponsoring.
>
> Let me settle things, provide sane package with format=3.0 (quilt),
> with pristine tar. I will ping once I am ready
control: tag -1 moreinfo
[2018-04-13 16:37] Gianfranco Costamagna
> Hello,
>
> >The next thing you might try is `git deborig`. But I understand just
> >asking Dmitry!
Hello. I am a bit lost about state of this RFS, but it seems I did
stupid thing with format=1.0; complicating sponsoring.
Let
Hello,
>The next thing you might try is `git deborig`. But I understand just
>asking Dmitry!
git deborig -f upstream/3.14
same effect, as well
as
git deborig -f v3.14...
G.
Hello,
On Fri, Apr 13 2018, Gianfranco Costamagna wrote:
>>Please try typing `origtargz`.
>
>
> it downloads the current one in the archive, without the patches, and
> then it fails with:
Ah, sorry, I thought it would invoke uscan.
The next thing you might try is `git deborig`. But I understan
Hello,
>Please try typing `origtargz`.
it downloads the current one in the archive, without the patches, and then it
fails with:
dpkg-source: warning: the diff modifies the following upstream files:
.git/HEAD
.git/config
.git/description
.git/hooks/applypatch-msg.sample
.git/hooks/commit-ms
Hello,
On Thu, Apr 12 2018, Gianfranco Costamagna wrote:
> I'm worried about the disappear of "debian-changes" patch, is it
> somewhere else? should I get a new orig tarball? I don't want my
> upload to make something disappear from the patch queue, due to my
> lack of dgit procedures.
It's bec
control: owner -1 !
control: tags -1 moreinfo
Hello Dmitry
sorry for taking too long for this one.
I did:
grab inotify-tools from experimental
grab the debian directory from the git repo, and debdiffed the results.
I'm worried about the disappear of "debian-changes" patch, is it somewhere
else? s
Hello,
On Wed, Feb 14 2018, Sean Whitton wrote:
> If you do this, please upload using `dgit push-source` since Dmitry is
> using a dgit-based workflow.
>
> (you can just run `dgit push-source` and it should do everything for
> you)
Oh, plus --overwrite since the last upload to unstable was not m
Hello Gianfranco,
On Wed, Feb 14 2018, kact...@gnu.org wrote:
> Hello! Gianfranco, could you please consider building and, probably,
> sponsoring this package? We have issue, that it FTBFS on Sean's setup,
> but builds on mine and on debomatic. As debomatic admin notified,
> debomatic is not out-
> > [2018-02-12 13:07] Sean Whitton
> >> > Last version is at bacef877c2f9293f9e1fd624b32d5306d7bc3c27 Maybe,
> >> > you could try again?
> >>
> >> Still FTBFSs. Log attached.
> >>
> >> I suspect that the debomatic sid chroot is out-of-date.
> >
> > Stange. Just did 'sbuild-update -udcar', and s
Hello Dmitry,
On Tue, Feb 13 2018, kact...@gnu.org wrote:
> [2018-02-12 13:07] Sean Whitton
>> > Last version is at bacef877c2f9293f9e1fd624b32d5306d7bc3c27 Maybe,
>> > you could try again?
>>
>> Still FTBFSs. Log attached.
>>
>> I suspect that the debomatic sid chroot is out-of-date.
>
> Stang
Hello,
On Tue, Feb 13 2018, Luca Falavigna wrote:
> 2018-02-13 4:18 GMT+01:00 :
>>> I suspect that the debomatic sid chroot is out-of-date.
>
> amd64 chroot was updated on Sunday, February 11, 2018 4:20:10 PM UTC
> (1518366010.2514317).
Thanks for the feedback!
--
Sean Whitton
signature.asc
2018-02-13 4:18 GMT+01:00 :
>> I suspect that the debomatic sid chroot is out-of-date.
amd64 chroot was updated on Sunday, February 11, 2018 4:20:10 PM UTC
(1518366010.2514317).
--
Cheers,
Luca
[2018-02-12 13:07] Sean Whitton
> > Last version is at bacef877c2f9293f9e1fd624b32d5306d7bc3c27 Maybe, you
> > could try again?
>
> Still FTBFSs. Log attached.
>
> I suspect that the debomatic sid chroot is out-of-date.
Stange. Just did 'sbuild-update -udcar', and still fails to reproduce.
I
Hello,
On Mon, Feb 12 2018, kact...@gnu.org wrote:
> Last version is at bacef877c2f9293f9e1fd624b32d5306d7bc3c27 Maybe, you
> could try again?
Still FTBFSs. Log attached.
I suspect that the debomatic sid chroot is out-of-date.
--
Sean Whitton
inotify-tools_3.14-4_amd64-2018-02-12T20:05:02Z
[2018-02-10 12:13] Sean Whitton
> - It FTBFSs for me. Log attached.
Look, debomatic build is succesful:
http://debomatic-amd64.debian.net/distribution#unstable/inotify-tools/3.14-4/buildlog
Last version is at bacef877c2f9293f9e1fd624b32d5306d7bc3c27
Maybe, you could try again?
[2018-02-10 12:13] Sean Whitton
> Review of 3c46a878fd294e9af9f8e7c225d16e8aceb960cf:
>
> - It looks like you added an entry to the changelog for 3.13-3 that
> should have been in the changelog for 3.13-4.
Good catch. Will fix it.
> - I'm not sure that DPKG_EXPORT_BUILDFLAGS = 1 will have an
control: tag -1 +moreinfo
control: owner -1 !
Hello Dmitry,
Review of 3c46a878fd294e9af9f8e7c225d16e8aceb960cf:
- It looks like you added an entry to the changelog for 3.13-3 that
should have been in the changelog for 3.13-4.
- I'm not sure that DPKG_EXPORT_BUILDFLAGS = 1 will have any effect
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "inotify-tools"
* Package name : inotify-tools
Version : 3.14-4
Upstream Author : Radu Voicilas
* Url : https://github.com/rvoicilas/inotify-tools/wiki/
* Lic
20 matches
Mail list logo
