Your message dated Sat, 28 Apr 2007 21:55:34 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#421397: libjasper-dev: please provide the old
libjasper-1.701-dev package
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: libjasper-dev
Version: 1.900.1-3
Severity: important
Hello.
I think it'd be good if libjasper-dev could Provide: the old
libjasper-1.701-dev package. This way the transition would be much
smoother, since it would not require uploads of about 20 packages.
Thanks,
--
Adeodato Simó dato at net.com.org.es
Debian Developer adeodato at debian.org
This is my boyfriend, Chester Fleet. [...] It's kind of a weird day to meet him
because he lost a bet with me, and that means that for the entire day, he can
only talk in clichés. It is so much fun.
-- Tana Schrick
--- End Message ---
--- Begin Message ---
Hi,
Adeodato Simó wrote:
> I think it'd be good if libjasper-dev could Provide: the old
> libjasper-1.701-dev package. This way the transition would be much
> smoother, since it would not require uploads of about 20 packages.
While this is technically feasible, I'm not sure if this is the right
solution, since the packages will need to be uploaded anyway, and
instead of 20, I can only find 3 of this kind:
grep "^Build-Depends" Sources | grep libjasper-1.7 | wc -l
... currently results in 6 entries, 3 of which already have
Build-Depends: " | libjasper-dev".
I'm closing this bug for now but feel free to convince me otherwise in
case I missed something.
Thanks for considering.
bye,
Roland
--- End Message ---
