The whole point of this transition is that the rebuilt library is not
compatible. So it can't provide the old name and there can't be a transitional
package.
Cheers
Julien
On August 9, 2015 8:25:46 AM CEST, Eriberto Mota eribe...@debian.org wrote:
Hi Julien,
I applied your patch and I updated
binary:libafflib0v5 is NEW.
Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be patient.
Packages are routinely processed through to the
FYI: The status of the hashrat source package
in Debian's testing distribution has changed.
Previous version: (not in testing)
Current version: 1.6.1-2
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you
Hi Julien,
Ok. I will do it:
1. Upload to experimental, without close the bug.
2. Notify all maintainers of dependent packages, allowing changes up
to next Saturday.
3. In next Saturday, upload to unstable, closing the bug.
4. Notify all maintainers that uploaded their packages to
sleuthkit_4.1.3-11_amd64.changes uploaded successfully to localhost
along with the files:
sleuthkit_4.1.3-11.dsc
sleuthkit_4.1.3-11.debian.tar.xz
libtsk-dev_4.1.3-11_amd64.deb
libtsk10v5_4.1.3-11_amd64.deb
sleuthkit_4.1.3-11_amd64.deb
Greetings,
Your Debian queue daemon
binary:libtsk10v5 is NEW.
Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be patient.
Packages are routinely processed through to the
Your message dated Sun, 09 Aug 2015 23:00:11 +
with message-id e1zozzb-0006dh...@franck.debian.org
and subject line Bug#790975: fixed in afflib 3.7.6-5
has caused the Debian Bug report #790975,
regarding afflib: library transition may be needed when GCC 5 is the default
to be marked as done.
Source: sleuthkit
Version: 4.1.3-11
Severity: normal
Although not a must in Debian policy, the preference is to not use embedded
copies of libraries. sleuthkit-4.1.3/framework/modules/c_LibExifModule has
an embedded copy of libexif-0.6.20 that is used during package build. It
would be better to
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 09 Aug 2015 16:15:18 -0300
Source: sleuthkit
Binary: sleuthkit libtsk10v5 libtsk-dev
Architecture: source amd64
Version: 4.1.3-11
Distribution: unstable
Urgency: medium
Maintainer: Debian Forensics
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 09 Aug 2015 02:09:04 -0300
Source: afflib
Binary: libafflib0v5 libafflib-dev afflib-dbg afflib-tools
Architecture: source amd64
Version: 3.7.6-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Forensics
Pour vous désabonner, rendez-vous sur cette page :
L'été des saveurs
-20%* sur votre commande avec le code SAVEURS
Et en plus de votre avantage : Livraison gratuite dès 49€ d'achats sur mondial
relay
Lots en promos jusqu'à -70%(1) Destockage jusqu'à -67%(2)
Nouveautés -15%* avec
Package: hashdeep
Version: 4.4-1
Severity: important
Dear Maintainer,
The removal of the symlinks that created the program
names md5deep, sha1deep, etc. destroys the ability of the
multi-call hashdeep progam to output and verify checksums
compatible with the equivalent GNU checksum utilities
On Sun, Aug 9, 2015 at 10:42:29 -0300, Eriberto wrote:
Hi Julien,
Ok. I will do it:
1. Upload to experimental, without close the bug.
2. Notify all maintainers of dependent packages, allowing changes up
to next Saturday.
3. In next Saturday, upload to unstable, closing the bug.
13 matches
Mail list logo
