-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
clarify changes required to dnspython library #17
Comments
|
I created a pull request and awaiting for the merge. |
|
Author was not interested to accept the pull request: rthalley/dnspython#163 |
|
i think i was able to somewhat change his mind - but now it requires more changes to dnsdiag, i think. is that something for which i should open a feature request or something? thanks for following up! |
|
I will make the changes based on the same ticket. On 30 May 2016, at 1:50, anarcat wrote:
|
|
Awesome, thanks!
|
|
@anarcat updated on dev branch. I am waiting for dnspython maintainer to upload new package to pypi so that I can merge with master. |
|
Hi, I currently have the ITP bug for dnsdiag in Debian- just waiting for this to be resolved before I proceed. |
|
I am waiting for dnspython maintainer to upload latest version to pypi. I queried them and haven't receive a response yet. |
|
@anarcat dnspython people updated their package on pypi with all the changes we needed. So I removed the local modified version of dnspython and now we depend on official dnspython from pypi. I pushed the changes and I believe you can package it for debian now. |
|
@farrokhi awesome, thanks! turns out that @ana-cc has taken over my "RFP" (Request For Package) and turned it into an "ITP" (Intend To Package) which is great news: someone else than me will take care of this. :) The ITP is here, if anyone wants to follow that progress, and I will notify that issue that this is fixed. |
Hi!
I am looking at packaging this for Debian and since the DNSpython library is already packaged in Debian, it is unclear how I will need to proceed.
What exactly are the changes required? Looking at the submodule, i see the following three commits:
... but those seem to be based on the upstream
python3branch, which doesn't seem to be merged with a release upstream.Is that accurate?
Would it be possible to make a pull request that would regularize the situation? :)
Thanks!
The text was updated successfully, but these errors were encountered: