severity 389711 important
thanks
Hi,
> [...]
as discussed, the issue needs to be fixed w/o upgrading exiv2 (and this
mail is "just" to make sure it is also written in the bug report).
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
On Saturday 09 December 2006 09:59, Andreas Barth wrote:
> * Mark Purcell ([EMAIL PROTECTED]) [061209 10:54]:
> > The discussion on debian-release seems to of died down and there doesn't
> > appear to be any dissent against uploading.
>
> Stop. We are really unhappy with transitions at the current
* Mark Purcell ([EMAIL PROTECTED]) [061209 10:54]:
> The discussion on debian-release seems to of died down and there doesn't
> appear to be any dissent against uploading.
Stop. We are really unhappy with transitions at the current time.
The only reason that I didn't send a "please don't do it"-
On Thursday 07 December 2006 14:13, KELEMEN Peter wrote:
> * Mark Purcell ([EMAIL PROTECTED]) [20061207 06:46]:
> > While we await a decision from debian-release. Could you post
> > packages to either experimental or people.debian.org so we can
> > start the integration.
>
> Sure. I have limited
* To Mark Purcell ([EMAIL PROTECTED]) [20061206 16:43]:
> I have an almost ready 0.12 packaged. 0.11 was skipped due to
> the misunderstandings around sonames and C++ ABI upgrades. The
> release managers allow upload of 0.12, I can do it today at
> midnight UTC. If you have changes other than t
debian-release,
We have a couple of nasty (RC) bugs against digikam (crashes startup)
caused if the user has corrupted meta-data within their JPEG images.
The crash is caused by poor handling of exiv2 libraries, which has been
fixed in subsequent revisions of exiv2. unstable has 0.10, upstream ha
6 matches
Mail list logo
