Re: Need help with NMU

2020-02-18 Thread SteveM
Woodrow,
Thank you for the assistance. I have been able to get further but am
stumpted by the upload to mentors.debian.org. My upload is getting
rejected:
timeshift dsc reference timeshift_19.01+ds.orig.tar.gz, but the file
was not found.
Please, include it in your upload.
I have this file, or rather the .tar.xz version of it so I need to
either not have the dsc file point to the orig.tar.gz or fix it to
point to the orig.tar.xz then get dput to inlude it in the upload. I
don't believe that it is needed as it already exits on
packages.debian.org/sid/timeshift.
Thank you for any help that anyone can provide in working through this
issue.-Steve Meliza
On Wed, 2020-02-19 at 00:24 +0800, Woodrow Shen wrote:
> Hi,
> If you try to find mentors to support NMU, I was suggested to use 
> https://mentors.debian.net/ to upload your package first, and you
> have to file a RFS bug against the sponsorship-requests[1] pseudo-
> package.
> I think fixing these bugs could be sequential.
> 
> Woodrow
> 
> [1] https://mentors.debian.net/sponsors
> On Tue, Feb 18, 2020 at 11:52 PM Steve M  wrote:
> > Hello,
> > I have never contributed before and am trying to make a NMU patch
> > to prevent package timeshift from being removed on 21Feb2020. The
> > autoremoval bug for timeshift is 948130 [1]. I attempted to contact
> > the maintainer 3 days ago but have not yet received a reply. This
> > leaves me little hope that this RC bug can be closed in time
> > without an NMU.
> > 
> > The fix is quite simple and was made in the upstream git repo, but
> > has not been released yet. I have built the package locally but am
> > at a loss of how to proceed next. I was lead to believe that using
> > nmudiff was the correct next step, but I’m afraid I’ve stuffed that
> > up as it made a new bug report [2] instead of sending it to the
> > existing bug [1].
> > 
> > Please advise on how I should proceed.
> > 
> > Thanks
> > -Steve Meliza
> > 
> > 
> > [1] https://bugs.debian.org/948130
> > [2] https://bugs.debian.org/951590
> > 


Re: Need help with NMU

2020-02-18 Thread Andrey Rahmatullin
On Tue, Feb 18, 2020 at 07:44:21AM -0800, Steve M wrote:
> Hello,
> 
> I have never contributed before and am trying to make a NMU patch to
> prevent package timeshift from being removed on 21Feb2020.
Note that autoremovals only remove from testing.

> The autoremoval bug for timeshift is 948130 [1]. I attempted to contact
> the maintainer 3 days ago but have not yet received a reply. 
3 days is very short.

> This leaves me little hope that this RC bug can be closed in time
> without an NMU.
There is a lot of time to fix it, after that it will migrate back to
testing.

> The fix is quite simple and was made in the upstream git repo, but has
> not been released yet. I have built the package locally but am at a loss
> of how to proceed next. 
Upload the package to mentors and file an RFS, like the other email says.


> I was lead to believe that using nmudiff was the
> correct next step, but I’m afraid I’ve stuffed that up as it made a new
> bug report [2] instead of sending it to the existing bug [1].
I guess that's because you don't close any bugs in the changelog entry so
nmudiff didn't know where to send the info.
Also, the template says "Uploaded" which isn't true, you need to rephrase
it as you didn't really upload anything yet.
Also, your diff is wrong: the changelog diff looks broken and the control
diff contains unrelated Depends and Build-Depends formatting changes.

-- 
WBR, wRAR


signature.asc
Description: PGP signature


Re: Need help with NMU

2020-02-18 Thread Woodrow Shen
Hi,

If you try to find mentors to support NMU, I was suggested to use
https://mentors.debian.net/ to upload your package first, and you have to
file a RFS bug against the sponsorship-requests[1] pseudo-package.
I think fixing these bugs could be sequential.

Woodrow

[1] https://mentors.debian.net/sponsors

On Tue, Feb 18, 2020 at 11:52 PM Steve M  wrote:

> Hello,
>
> I have never contributed before and am trying to make a NMU patch to
> prevent package timeshift from being removed on 21Feb2020. The autoremoval
> bug for timeshift is 948130 [1]. I attempted to contact the maintainer 3
> days ago but have not yet received a reply. This leaves me little hope that
> this RC bug can be closed in time without an NMU.
>
> The fix is quite simple and was made in the upstream git repo, but has not
> been released yet. I have built the package locally but am at a loss of how
> to proceed next. I was lead to believe that using nmudiff was the correct
> next step, but I’m afraid I’ve stuffed that up as it made a new bug report
> [2] instead of sending it to the existing bug [1].
>
> Please advise on how I should proceed.
>
> Thanks
> -Steve Meliza
>
>
> [1] https://bugs.debian.org/948130
> [2] https://bugs.debian.org/951590
>
>


Need help with NMU

2020-02-18 Thread Steve M
Hello,

I have never contributed before and am trying to make a NMU patch to prevent 
package timeshift from being removed on 21Feb2020. The autoremoval bug for 
timeshift is 948130 [1]. I attempted to contact the maintainer 3 days ago but 
have not yet received a reply. This leaves me little hope that this RC bug can 
be closed in time without an NMU.

The fix is quite simple and was made in the upstream git repo, but has not been 
released yet. I have built the package locally but am at a loss of how to 
proceed next. I was lead to believe that using nmudiff was the correct next 
step, but I’m afraid I’ve stuffed that up as it made a new bug report [2] 
instead of sending it to the existing bug [1].

Please advise on how I should proceed.

Thanks
-Steve Meliza


[1] https://bugs.debian.org/948130 
[2] https://bugs.debian.org/951590