[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#560841: marked as done (binNMUs: getting rid of libfreebsd0 (specific to kfreebsd-*))

Your message dated Sun, 13 Dec 2009 00:20:13 +0100
with message-id <4B24252D.2010004@debian.org>
and subject line Re: Bug#560841: binNMUs: getting rid of libfreebsd0 (specific to kfreebsd-*)
has caused the Debian Bug report #560841,
regarding binNMUs: getting rid of libfreebsd0 (specific to kfreebsd-*)
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 owner@bugs.debian.org
immediately.)


-- 
560841: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560841
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal

Hi,

Petr Salinger kindly reported this round of binNMUs should help getting
rid of libfreebsd0. I've proceeded as follow on kfreebsd-amd64:
| $ cupt source --download-only afuse avfs bindfs curlftpfs fuse-convmvfs fusedav gphotofs mhddfs mythtvfs-fuse linux-ntfs python-fuse rofs-fuse sshfs-fuse vmfs-tools
| $ for i in *dsc ; do sudo pbuilder --build $i ; done
| $ for j in $(for i in *.dsc ; do dcmd /var/cache/pbuilder/result/${i%%.dsc}_kfreebsd-amd64.changes |grep \\.deb$; done); do dpkg --info $j ;done|grep freebsd

It seems that all packages built successfully, and that there's no
Depends: left on libfreebsd0.

So please schedule those binNMUs when you find it suitable:
  nmu afuse_0.2-3 . kfreebsd-amd64 kfreebsd-i386 . -m 'Rebuild to drop libfreebsd0.'
  nmu avfs_0.9.8-6 . kfreebsd-amd64 kfreebsd-i386 . -m 'Rebuild to drop libfreebsd0.'
  nmu bindfs_1.8.3-2 . kfreebsd-amd64 kfreebsd-i386 . -m 'Rebuild to drop libfreebsd0.'
  nmu curlftpfs_0.9.2-1 . kfreebsd-amd64 kfreebsd-i386 . -m 'Rebuild to drop libfreebsd0.'
  nmu fuse-convmvfs_0.2.4-2 . kfreebsd-amd64 kfreebsd-i386 . -m 'Rebuild to drop libfreebsd0.'
  nmu fusedav_0.2-2 . kfreebsd-amd64 kfreebsd-i386 . -m 'Rebuild to drop libfreebsd0.'
  nmu gphotofs_0.4.0-3 . kfreebsd-amd64 kfreebsd-i386 . -m 'Rebuild to drop libfreebsd0.'
  nmu linux-ntfs_2.0.0-1 . kfreebsd-amd64 kfreebsd-i386 . -m 'Rebuild to drop libfreebsd0.'
  nmu mhddfs_0.1.27-1 . kfreebsd-amd64 kfreebsd-i386 . -m 'Rebuild to drop libfreebsd0.'
  nmu mythtvfs-fuse_0.6.1-1 . kfreebsd-amd64 kfreebsd-i386 . -m 'Rebuild to drop libfreebsd0.'
  nmu python-fuse_0.2-2 . kfreebsd-amd64 kfreebsd-i386 . -m 'Rebuild to drop libfreebsd0.'
  nmu rofs-fuse_2006.11.28-2 . kfreebsd-amd64 kfreebsd-i386 . -m 'Rebuild to drop libfreebsd0.'
  nmu sshfs-fuse_2.2-1 . kfreebsd-amd64 kfreebsd-i386 . -m 'Rebuild to drop libfreebsd0.'
  nmu vmfs-tools_0.2.0-1 . kfreebsd-amd64 kfreebsd-i386 . -m 'Rebuild to drop libfreebsd0.'
  
Thanks for considering.

Mraw,
KiBi.

--- End Message ---
--- Begin Message --- 
Cyril Brulebois wrote:
> Package: release.debian.org
> Severity: normal
> 
> Hi,
> 
> Petr Salinger kindly reported this round of binNMUs should help getting
> rid of libfreebsd0. I've proceeded as follow on kfreebsd-amd64:
> | $ cupt source --download-only afuse avfs bindfs curlftpfs fuse-convmvfs fusedav gphotofs mhddfs mythtvfs-fuse linux-ntfs python-fuse rofs-fuse sshfs-fuse vmfs-tools
> | $ for i in *dsc ; do sudo pbuilder --build $i ; done
> | $ for j in $(for i in *.dsc ; do dcmd /var/cache/pbuilder/result/${i%%.dsc}_kfreebsd-amd64.changes |grep \\.deb$; done); do dpkg --info $j ;done|grep freebsd
> 
> It seems that all packages built successfully, and that there's no
> Depends: left on libfreebsd0.
> 
> So please schedule those binNMUs when you find it suitable:

All scheduled.

>   nmu python-fuse_0.2-2 . kfreebsd-amd64 kfreebsd-i386 . -m 'Rebuild to drop libfreebsd0.'

This should have been _2:0.2-2. One can also list the packages all at
once similar to the architectures btw.

Thanks for reporting.

Cheers

Luk

--- End Message ---
Reply to: