This bug was fixed in the package epigrass - 2.0b3~dfsg-1
---
epigrass (2.0b3~dfsg-1) unstable; urgency=low
[ Charles Plessy ]
* New upstream release (LP: #271789).
* debian/control:
- Switch to debhelper 7 (also in debian/compat).
- Dropped versionned dependency on CDB
Thanks,
I 'll certainly include the LaTeX in the next release.
Flávio
On Sun, May 3, 2009 at 8:17 AM, Charles Plessy wrote:
> Thanks a lot for the fast answer,
>
> We are preparing an updated package with version 2.0b3. As in previous
> versions, we have to remove the PDF documentation as the
Thanks a lot for the fast answer,
We are preparing an updated package with version 2.0b3. As in previous
versions, we have to remove the PDF documentation as the absence of its
sources make it a non-free document according to our guidelines. It
would be much appreciated if your next release could
Hi Charles,
Current sources are currently not being kept on sourceforge. Latest tarballs
are being made available through PyPI:
http://pypi.python.org/pypi?%3Aaction=pkg_edit&name=epigrass
I intend to move the latest source back to sourceforge soon, now that they
support Mercurial.
Thanks for t
Dear Flávio,
I am member of the Debian Med packaging team; Ubuntu’s epigrass package
was imported from Debian. Sorry for having neglected Epigrass so long:
Debian was frozen between August 2008 and February 2009.
I had a look at the SourceForge page: I could not find the 2.0b2 tarball
and the 2.0
Oops, sorry about that.
--
New upstream release of epigrass (2.0)
https://bugs.launchpad.net/bugs/271789
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/m
epigrass is already packaged.
** Summary changed:
- [needs-packaging] epigrass 2.0
+ New upstream release of epigrass (2.0)
** Tags removed: needs-packaging
** Changed in: epigrass (Ubuntu)
Importance: Undecided => Wishlist
Status: New => Triaged
** Tags added: upgrade
--
New upstr
