Upload of fuse to t-p-u, binNMUs required
Hi,
with the maintainers' consent, I have just tried to upload
fuse_2.5.3_4.2 to testing-proposed-updates, fixing bug #409644 for etch.
It didn't work, claiming there was already such a version in the "Done"
directory. Apparently someone else has already done it.
Please accept it, and (assuming the bug has been addressed by the NMU)
trigger binNMUs for the build-depending packages. This has been
discussed on #debian-release on monday, see the log extract at the
bottom of this mail.
I have checked whether the build-depending packages are binNMU-safe.
The following source packages build only one binary package, or do not
have any interdependencies among multiple binary packages:
afuse
beaglefs
curlftpfs
encfs
fusesmb
gphotofs
libfuse-perl
obexfs
python-fuse
sshfs-fuse
***************************************************
Not 100% clear, but I *think* safe are the following:
1. libfusefs-ruby
builds two binary packages, among which the arch-all one,
libfusefs-ruby, just
Depends: libfusefs-ruby1.8
so I guess it is safe
2. linux-ntfs
builds lots of binary packages, but there is only one with
interdependencies:
Package: libntfs9
Section: libs
Architecture: any
Depends: ${shlibs:Depends}
...
Package: libntfs-dev
Section: libdevel
Architecture: any
Depends: libntfs9 (= ${Source-Version})
a problem, however, might be that it also builds a udeb:
Package: ntfsprogs-udeb
Section: debian-installer
Architecture: any
XC-Package-Type: udeb
Depends: ${shlibs:Depends}
Provides: ntfstools-udeb
Description: Tools for doing neat things in NTFS partitions from Linux - udeb
Currently this udeb contains only ntfsresize.
(and since ntfsprogs itself depends on fuse-utils, I guess this one
also contains the functionality which causes a dependence on libfuse2).
3. ntfs-3g
Builds
Package: libntfs-3g0
Section: libs
Architecture: any
Depends: ${shlibs:Depends}
and
Package: libntfs-3g-dev
Section: libdevel
Architecture: any
Depends: libntfs-3g0 (= ${binary:Version})
this seems to be safe, since both are arch-any.
Regards, Frank
(18:00:06) jcristau: formorer: it's only RC if it breaks upgrades from sarge (which it probably does, anyway)
(18:00:40) formorer: jcristau: and the question wasn't RCness but practical relevance :)
(18:00:42) fant: formorer,jcirstau: It would break upgrades from sarge only if the library is used before it is upgraded.
(18:00:44) formorer: but its indeed RC
(18:01:16) jcristau: fant: partial upgrades are supposed to work
[...]
(18:07:06) fant: jcristau,formorer: Can we be sure there are no packages in etch which depend on libfuse2 without a proper version?
(18:07:27) fant: If there are any, they might need a binNMU, because just fixing the shlibs file in the dev package won't help, will it?
(18:07:45) ***pusling thinks rebuilds are neeeeded
[...]
(18:09:54) jcristau: fant: yeah, they will need rebuilds
(18:13:01) fant: jcristau: grep-dctrl (covering Build-Depends in etch/{main,contrib,non-free}, plus B-D-I because I'm paranoid) sayst there are 13 packages affected:
(18:13:11) fant: afuse beaglefs curlftpfs encfs fusesmb gphotofs libfuse-perl libfusefs-ruby linux-ntfs ntfs-3g obexfs python-fuse sshfs-fuse
(18:13:48) jcristau: I'd have grepped for packages Depending on libfuse2
(18:17:09) fant: jcristau: That gives essentially the same. s/libfusefs-ruby/libfusefs-ruby1.8/;s/linux-ntfs/ntfsprogs/;s/sshfs-fuse/sshfs/
(18:17:16) fant: (pluse libfuse-dev)
--
Dr. Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)
Reply to: