Re: Right way to submit patches for Ubuntu packages
Hello everyone. Quite some time ago a guy wanted to learn how to add packages to the repo and he asked me if it was ok for him to use my project as a test case. I said sure! So he added LaserBoy. I have done a whole lot of development on this project since then and I would like to get the latest version in the repo. I'd also like to know how to keep it current into the future. Could someone please contact me directly and help me get this done? After that, I have another nice open source project called ezfb that is a Linux Frame Buffer (video card) API that I would also like to submit. But I have a little bit of updating to do on that one. Thank you in advance. http://laserboy.org/code/LaserBoy_Curreent.zip mailto:ja...@akrobiz.com James.-- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Right way to submit patches for Ubuntu packages
Following up on this, it has been a couple weeks since the EE cycle started, but there doesn't seem to be any activity on that patch. Could it have something to do with the package seemingly tracking the GDB git version directly instead of Debian's packaging of it? Jonathan On Fri, Apr 12, 2019 at 7:08 PM Dimitri John Ledkov wrote: > Hi, > > On Fri, 12 Apr 2019 at 22:26, Jonathan Behrens wrote: > > > > I've been trying to get a two line patch merged for `gdb-multiarch`. > Debian accepted it almost right away, but subsequent releases for Ubuntu > haven't included it. About a month ago I tried submitting directly on > Launchpad but that has seemingly been ignored as well. Have I submitted the > patch incorrectly? Or is there some reason that it shouldn't be merged? > > > > Ubuntu normally merges packaging changes from Debian continuously > whilst the development is open up to the Debian Import Freeze / > Feature Freeze. Which for the Disco Dingo release was on 21st of > February. > I think your patch was uploaded into debian on the 22nd of February. > And whilst we do fix, merge and upload things post Feature Freeze it's > progressively more conservative / higher priority things. > I am afraid, that bugfix, possibly missed the 19.04 cycle by a day, > effectively. > Once we open EE cycle for development, I'm sure it will be merged into > Ubuntu then =/ > > Sorry about that. > > > -- > Regards, > > Dimitri. > -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Right way to submit patches for Ubuntu packages
[dropping bystanders from Cc:, leaving only Dan and the list] Thank you for volunteering to help with Ubuntu! On Sat, Apr 13, 2019 at 08:30:06AM -0700, Dan Kegel wrote: > Any advice for the next step in navigating > https://wiki.ubuntu.com/StableReleaseUpdates ? https://wiki.ubuntu.com/StableReleaseUpdates#Procedure tries to document what is needed step-by-step. Is there anything particular in this list you need help with? This list is the right place to ask, but I don't really know where I can start to answer your question apart from pointing to that list. > Or is a word to a python maintainer more appropriate? We can ask the usual suspects for code review once you're ready with some proposed uploads. HTH, Robie signature.asc Description: PGP signature -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Right way to submit patches for Ubuntu packages
In a similar vein, my ppa https://launchpad.net/~dank/+archive/ubuntu/python-fixes has a couple cherrypicked fixes for the python ecosystem in ubuntu 16.04 and 18.04. I put that together as I was fixing https://github.com/nexB/scancode-toolkit to install via system pip; turns out there were a couple problems that could not be fixed without a couple fixes in ubuntu's python packages. Any advice for the next step in navigating https://wiki.ubuntu.com/StableReleaseUpdates ? Or is a word to a python maintainer more appropriate? Thanks, Dan -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Right way to submit patches for Ubuntu packages
Hi, On Fri, 12 Apr 2019 at 22:26, Jonathan Behrens wrote: > > I've been trying to get a two line patch merged for `gdb-multiarch`. Debian > accepted it almost right away, but subsequent releases for Ubuntu haven't > included it. About a month ago I tried submitting directly on Launchpad but > that has seemingly been ignored as well. Have I submitted the patch > incorrectly? Or is there some reason that it shouldn't be merged? > Ubuntu normally merges packaging changes from Debian continuously whilst the development is open up to the Debian Import Freeze / Feature Freeze. Which for the Disco Dingo release was on 21st of February. I think your patch was uploaded into debian on the 22nd of February. And whilst we do fix, merge and upload things post Feature Freeze it's progressively more conservative / higher priority things. I am afraid, that bugfix, possibly missed the 19.04 cycle by a day, effectively. Once we open EE cycle for development, I'm sure it will be merged into Ubuntu then =/ Sorry about that. -- Regards, Dimitri. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
