Your message dated Sun, 20 Nov 2011 22:17:40 +0000
with message-id <[email protected]>
and subject line Bug#636801: fixed in argyll 1.3.5-1
has caused the Debian Bug report #636801,
regarding argyll and libicc2 packages are based on same tarball, they should
get merged
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
636801: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636801
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: argyll
Version: 1.3.0-3
The packages argyll and libicc2 are both taking their source code from
the upstream source tarball of Argyll. Having two (or more) different
packages based on the same source code tarball one will easily get into
a maintenance nightmare. If a security vulnerability shows up in the
upstream code, all packages based on it need their upstream tarball be
updated and rebuilt. One can easily forget one package and so the
vulnerability stays in the forgotten package.
I am introducing Color Management in Ubuntu and therefore I have updated
the Argyll package to version 1.3.3 and also created a merged package
(but not uploaded to Ubuntu). You can download it here:
http://www.openprinting.org/download/tmp/argyll_1.3.3.orig.tar.gz
http://www.openprinting.org/download/tmp/argyll_1.3.3-0ubuntu2.dsc
http://www.openprinting.org/download/tmp/argyll_1.3.3-0ubuntu2.debian.tar.gz
Problem is that the version number used for libicc is the API/ABI
version number 2.12 which is much higher than the 1.3.3 of the upstream
tarball. Ho should I proceed to make the resulting package being well
accepted by Debian? Should I introduce an epoch? Or can a binary package
have another version number than its source package?
The mentioned package uses an epoch, but please tell me how to do it
correctly.
the merged package builds Argyll using the upstream Jam architecture,
this makes maintenance much easier than with a packager-supplied
autoconf/automake environment. Only libicc is built in a separate
directory using the very simple autoconf/automake files from the former
libicc2 package. This is done because the Jam environment has no
functionality to create shared libraries.
The package is a merger of Ubuntu packages, therefore it has Ubuntu
release numbers, change them if you want to use this package in Debian.
Till
--- End Message ---
--- Begin Message ---
Source: argyll
Source-Version: 1.3.5-1
We believe that the bug you reported is fixed in the latest version of
argyll, which is due to be installed in the Debian FTP archive:
argyll-dbg_1.3.5-1_amd64.deb
to main/a/argyll/argyll-dbg_1.3.5-1_amd64.deb
argyll_1.3.5-1.debian.tar.gz
to main/a/argyll/argyll_1.3.5-1.debian.tar.gz
argyll_1.3.5-1.dsc
to main/a/argyll/argyll_1.3.5-1.dsc
argyll_1.3.5-1_amd64.deb
to main/a/argyll/argyll_1.3.5-1_amd64.deb
argyll_1.3.5.orig.tar.bz2
to main/a/argyll/argyll_1.3.5.orig.tar.bz2
libicc-dev_2.12+argyll1.3.5-1_amd64.deb
to main/a/argyll/libicc-dev_2.12+argyll1.3.5-1_amd64.deb
libicc2_2.12+argyll1.3.5-1_amd64.deb
to main/a/argyll/libicc2_2.12+argyll1.3.5-1_amd64.deb
libimdi-dev_1.3.5-1_amd64.deb
to main/a/argyll/libimdi-dev_1.3.5-1_amd64.deb
libimdi0_1.3.5-1_amd64.deb
to main/a/argyll/libimdi0_1.3.5-1_amd64.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
[email protected] (supplier of updated argyll package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Sun, 13 Nov 2011 15:30:42 +0100
Source: argyll
Binary: argyll argyll-dbg libicc-dev libicc2 libimdi-dev libimdi0
Architecture: source amd64
Version: 1.3.5-1
Distribution: unstable
Urgency: low
Maintainer: Christian Marillat <[email protected]>
Changed-By: [email protected]
Description:
argyll - Color Management System, calibrator and profiler
argyll-dbg - debugging symbols for argyll
libicc-dev - Development files for the ICC profile I/O library
libicc2 - ICC profile I/O library
libimdi-dev - Development files for the IMDI library
libimdi0 - Integer Multi-Dimensional Interpolation routines (IMDI) library
Closes: 611139 622620 634688 636801 647093
Changes:
argyll (1.3.5-1) unstable; urgency=low
.
[ Christian Marillat ]
* New maintainer (Closes: #622620) Thanks, Roland!
* Use dh-autoreconf.
.
[ Dmitry Nezhevenko ]
* New upstream release (Closes: #647093).
* Switch to dpkg-source 3.0 (quilt) format.
* Merge debian changes from 1.3.0 (experimental) and 1.1.1 (unstable).
* Unsplit libicc2, built from the same source package again (since
upstream only ships it as part of Argyll anyway). Actually was already
done in experimental (Closes: #636801).
* Use kfreebsd-any instead of kfreebsd-(i386|amd64) to match kFreeBSD
(Closes: #634688).
* Provide dedicated libimdi0/libimdi-dev libraries (Closes: #611139).
* Add argyll-dbg package with debug symbols.
Checksums-Sha1:
7db37c29e82eb8bff70d7b310ca7d57d2d79f167 1645 argyll_1.3.5-1.dsc
9e58dcce83f1449b74490cda7f504b2da30de628 10850762 argyll_1.3.5.orig.tar.bz2
8e209e9b41917d209aeafd5741dec747684099a7 32666 argyll_1.3.5-1.debian.tar.gz
804f6d15c3a0cd0fda535c260aedc191dc308225 164712
libicc2_2.12+argyll1.3.5-1_amd64.deb
6b4384ad46016257ec93a3e6e53bd82542c30dd3 186308
libicc-dev_2.12+argyll1.3.5-1_amd64.deb
d8d11b1e8a09f3b89e4e7f738239d231dd6e9d9c 4483152 argyll_1.3.5-1_amd64.deb
14a84b6c8b4e5519310b5ab44d7017f2b812372e 3229170 argyll-dbg_1.3.5-1_amd64.deb
81032cd02901a60cc1d5f3f5d361c81e750b5769 299348 libimdi-dev_1.3.5-1_amd64.deb
3a5f2d092d1fb1c2a2e603226329cb4215501abe 300298 libimdi0_1.3.5-1_amd64.deb
Checksums-Sha256:
3d14969a205a4cc45e94ffea4bf267e6d5d786474cb31c127673d79826337e7e 1645
argyll_1.3.5-1.dsc
6bdf18862e60d2a9fcaddb6bcaf1b54f3442ab56a92e144a032eccce607c36fc 10850762
argyll_1.3.5.orig.tar.bz2
e628f1994ad832e6f4c1bf63a32fb846d59c92937f25bfb97259a02565c8dc8b 32666
argyll_1.3.5-1.debian.tar.gz
3a21bdbf2bc1628b6b4fe61c424344650b983a9f1653d4172e20c4d05da77221 164712
libicc2_2.12+argyll1.3.5-1_amd64.deb
22f8f4132da80b220c1cd5b4de4d91d6a057365cef05039cef76099c95e2918a 186308
libicc-dev_2.12+argyll1.3.5-1_amd64.deb
8e147781b544b14405c952811704e041b47ee9765d3549f8a040d561a25fb659 4483152
argyll_1.3.5-1_amd64.deb
b9dbbf235da4da146b9fb5d18695dc3c5afccda54415704ca193f28fcd7c90d1 3229170
argyll-dbg_1.3.5-1_amd64.deb
96a1445a1238dc2ad7e5d597f685728b96a7c0b8d53642dd0239995d39ff949d 299348
libimdi-dev_1.3.5-1_amd64.deb
fdc4c19b4d7ba415fdcea6987b15954da5756a087628473efc3e39d8e2f147ea 300298
libimdi0_1.3.5-1_amd64.deb
Files:
6e7fe18d2cba0d8667e6832b39626300 1645 graphics optional argyll_1.3.5-1.dsc
1a5e5ab25be96d7c1354f5803a73d500 10850762 graphics optional
argyll_1.3.5.orig.tar.bz2
a713daffb2ee7b911c61bfc2ffae82b8 32666 graphics optional
argyll_1.3.5-1.debian.tar.gz
f24648eb8ee7f6e602371d01b664f36c 164712 libs optional
libicc2_2.12+argyll1.3.5-1_amd64.deb
f6cc953ce4c53e56a5b90acc62c1130d 186308 libdevel optional
libicc-dev_2.12+argyll1.3.5-1_amd64.deb
6ae8303b327f20674b29fb90c990a4d4 4483152 graphics optional
argyll_1.3.5-1_amd64.deb
65830700948c202745339d1328c693df 3229170 debug extra
argyll-dbg_1.3.5-1_amd64.deb
37d0146303a4c037a57da882ddf631b5 299348 libdevel optional
libimdi-dev_1.3.5-1_amd64.deb
529bb5edb78a1c2a1f1581f9288ff72d 300298 libs optional
libimdi0_1.3.5-1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iD8DBQFOx84FB9xWPR9BuQcRApN2AKCQC/tz3Ejp3oYMI3Y5A22X/YEmRACfRSuv
fiJGHKsm3+8z4vDEuo8dqu4=
=v7aA
-----END PGP SIGNATURE-----
--- End Message ---
