Re: packaging gtkwave and icarus verilog
2009/3/12 Iztok Jeras iztok.je...@gmail.com Gtkwave is based on a stable version tarball and should be ready for jaunty. Only the version name should be changed and the mails and webpage of the official maintainer team added. http://gtkwave.sourceforge.net/ Hello Iztok, We are in Feature Freeze [0] so this will need an exception. Please see [1] for how to request an exception. Iulian [0] https://wiki.ubuntu.com/JauntyReleaseSchedule [1] https://wiki.ubuntu.com/FreezeExceptionProcess -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: packaging gtkwave and icarus verilog
Thanks for your help. I decided that since Ubuntu is in a Feature Freeze state, it would be better to keep my packages in a PPA (with corrected version string) and contact the Debian developers for their unstable release. I wish you a painless release, Iztok Jeras Hello Iztok, We are in Feature Freeze [0] so this will need an exception. Please see [1] for how to request an exception. Iulian [0] https://wiki.ubuntu.com/JauntyReleaseSchedule [1] https://wiki.ubuntu.com/FreezeExceptionProcess -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: packaging gtkwave and icarus verilog
Maybe could help you see this: https://wiki.ubuntu.com/SponsorshipProcess -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: packaging gtkwave and icarus verilog
I need help in naming the versions of PPA packages. The instructions are not very clear, and I did not check many examples. Please make suggestions. Looking at what you've done, you almost have it. X.Y-1~1 is smaller than X.Y-1 this allows the PPA package to be replaced by the official Ubuntu package once it enters the archive. So you have gtkwave (3.2.0-2~ppa1) in your archive. The problem is that both Debian and Ubuntu only have version gtkwave (3.1.13-1). The first Debian upload of this version would be: 3.2.0-1 If Ubuntu decided to package the new upstream release before Debian, it would be: 3.2.0-0ubuntu1 If Ubuntu uses the Debian package and modifies it, it would be: 3.2.0-1ubuntu1 The package in your PPA would replace any of those versions above as X.Y-2, even if it's X.Y-2~1, is always bigger than X.Y-1. Your package should have been: 3.2.0-0ubuntu1~ppa1 or 3.2.0-1~ppa1 Hope that makes sense, - Andrew Starr-Bochicchioo Ubuntu Contributing Developer -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: packaging gtkwave and icarus verilog
It does make sense, thanks. On Thu, Mar 12, 2009 at 6:23 PM, Andrew a.star...@gmail.com wrote: I need help in naming the versions of PPA packages. The instructions are not very clear, and I did not check many examples. Please make suggestions. Looking at what you've done, you almost have it. X.Y-1~1 is smaller than X.Y-1 this allows the PPA package to be replaced by the official Ubuntu package once it enters the archive. So you have gtkwave (3.2.0-2~ppa1) in your archive. The problem is that both Debian and Ubuntu only have version gtkwave (3.1.13-1). The first Debian upload of this version would be: 3.2.0-1 If Ubuntu decided to package the new upstream release before Debian, it would be: 3.2.0-0ubuntu1 If Ubuntu uses the Debian package and modifies it, it would be: 3.2.0-1ubuntu1 The package in your PPA would replace any of those versions above as X.Y-2, even if it's X.Y-2~1, is always bigger than X.Y-1. Your package should have been: 3.2.0-0ubuntu1~ppa1 or 3.2.0-1~ppa1 Hope that makes sense, - Andrew Starr-Bochicchioo Ubuntu Contributing Developer -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
