Your message dated Tue, 09 Oct 2012 17:12:57 +0200
with message-id <[email protected]>
and subject line Re: Bug#690052: nmu: genometools_1.4.2-2
has caused the Debian Bug report #690052,
regarding nmu: genometools_1.4.2-2
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.)
--
690052: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690052
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: binnmu
nmu genometools_1.4.2-2 . amd64 . -m "Rebuild in a clean Debian sid
environment."
genometools/amd64 unsatisfiable Depends: libc6 (>= 2.14)
libgenometools0/amd64 unsatisfiable Depends: libc6 (>= 2.14)
Looks like a package built on Ubuntu was uploaded to Debian ...
@Sascha (and your sponsor): in the future, please build the packages you
are uploading to Debian in a sid chroot. pbuilder/cowbuilder may be a
handy tools for this ...
Andreas
--- End Message ---
--- Begin Message ---
On 09/10/2012 17:01, Sascha Steinbiss wrote:
> On 10/09/2012 04:40 PM, Andreas Beckmann wrote:
>> genometools/amd64 unsatisfiable Depends: libc6 (>= 2.14)
>> libgenometools0/amd64 unsatisfiable Depends: libc6 (>= 2.14)
>>
>> Looks like a package built on Ubuntu was uploaded to Debian ...
>> @Sascha (and your sponsor): in the future, please build the packages you
>> are uploading to Debian in a sid chroot. pbuilder/cowbuilder may be a
>> handy tools for this ...
>
> Hi Andreas, thanks for the hint. I have actually noticed this earlier
> today and did exactly as you suggested, i.e. built a new package using
> pbuilder in a clean sid environment. This relaxed the libc dependency to
>> =2.11, which looks more reasonable.
>
> Sorry for the inconvenience -- I will check more carefully next time.
>
I can confirm that -4 doesn't have the reported issue.
$ grep-archive -f sid:ALL: -XP genometools
Package: genometools
Architecture: amd64
Depends: libbz2-1.0, libc6 (>= 2.11), libcairo2 (>= 1.2.4), libexpat1
(>= 2.0.1), libglib2.0-0 (>= 2.12.0), liblua5.1-0, libncurses5 (>=
5.5-5~), libpango1.0-0 (>= 1.22.0), libsqlite3-0 (>= 3.5.9), libtinfo5,
lua-filesystem, lua-lpeg, lua-md5, zlib1g (>= 1:1.2.3.3), genometools-common
Priority: extra
Version: 1.4.2-4
$ grep-archive -f sid:ALL: -XP libgenometools0
Package: libgenometools0
Architecture: amd64
Depends: libbz2-1.0, libc6 (>= 2.11), libcairo2 (>= 1.2.4), libexpat1
(>= 2.0.1), libglib2.0-0 (>= 2.12.0), liblua5.1-0, libpango1.0-0 (>=
1.22.0), libsqlite3-0 (>= 3.5.9), lua-filesystem, lua-lpeg, lua-md5,
zlib1g (>= 1:1.2.3.3), genometools-common
Priority: extra
Source: genometools
Version: 1.4.2-4
I'm closing this bugreport now. Thanks to Andreas for spotting this!
Regards,
--
Mehdi Dogguy مهدي الدڤي
--- End Message ---
