Control: reopen -1
Control: reassing -1 dmsetup
Control: found -1 2:1.02.77-2

On Du, 09 iun 13, 15:21:54, Yusuf Iskenderoglu wrote:
> Maybe, this information about device-mapper is also helpful for you. 
> IMHO, these are definitely the device-mapper subsystem, just as noted in
> my ticket.

Hi Yusuf,

If you don't report the bug against the correct package it will not be 
seen by the Maintainer. Based on your information below I'm reassigning 
it to dmsetup. Also, please use

    reportbug dmsetup

to follow-up and include package specific information (also missing 
because you filled the bug against an inexistent package).

Thanks for your time,
Andrei

> Regards,
> Yusuf
> 
> dreadnought:~# dpkg -l 'libdev*'
> Desired=Unknown/Install/Remove/Purge/Hold
> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name                                         Version                     
> Architecture                Description
> +++-============================================-===========================-===========================-=============================================================================================
> un  libdevel-dprof-perl                          <none>                       
>                            (no description available)
> ii  libdevmapper-dev                             2:1.02.77-1                 
> amd64                       Linux Kernel Device Mapper header files
> ii  libdevmapper-event1.02.1:amd64               2:1.02.77-1                 
> amd64                       Linux Kernel Device Mapper event support library
> un  libdevmapper1.02                             <none>                       
>                            (no description available)
> ii  libdevmapper1.02.1:amd64                     2:1.02.77-1                 
> amd64                       Linux Kernel Device Mapper userspace library
> dreadnought:~# dpkg -l 'dmsetup*'
> Desired=Unknown/Install/Remove/Purge/Hold
> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name                                         Version                     
> Architecture                Description
> +++-============================================-===========================-===========================-=============================================================================================
> ii  dmsetup                                      2:1.02.77-1                 
> amd64                       Linux Kernel Device Mapper userspace library
> 
> 
> 
> On So, 2013-06-09 at 15:16 +0200, Yusuf Iskenderoglu wrote:
> > Hi,
> > 
> > It was my intention to emphasize the problem with the device-mapper
> > subsystem inside the lvm2 package.
> > The problem is not lvm2 itself, however the device mapper.
> > 
> > Anyway, it is up to you. I just wanted to be helpful. If you think that
> > this bugreport was not helpful, and want more from me, than I will
> > disappoint you.
> > I am not interested in opening another bugreport, since the solution was
> > simply to downgrade some parts of the lvm2 update. It was complicated
> > enough to decide which section of the policy is being violated with that
> > bug. 
> > 
> > Have a nice weekend
> > Yusuf.
> > 
> > On So, 2013-06-09 at 14:11 +0300, Andrei POPESCU wrote:
> > > On Du, 09 iun 13, 10:02:04, Yusuf Iskenderoglu wrote:
> > > > Package: device-mapper
> > > > Version: 1.02.77-2
> > > > Severity: serious
> > > > Justification: Policy 10.5
> > > ...
> > > > The problem seems to relate to device mapper update from 1.02.77-1 to
> > > > 1.02.77-2.
> > > > However, in the same run, also lvm is replaced from 2.02.98-1 to 
> > > > 2.02.98-2.
> > > 
> > > Dear Yusuf,
> > > 
> > > There is no device-mapper package in Debian, only dmraid, which has 
> > > other versions than what you seem to be using:
> > > 
> > > $ rmadison dmraid
> > >  dmraid | 1.0.0.rc16-4.1 | squeeze | source, amd64, armel, i386, ia64, 
> > > mips, mipsel, powerpc, s390, sparc
> > >  dmraid | 1.0.0.rc16-4.2 | wheezy  | source, amd64, armel, armhf, i386, 
> > > ia64, mips, mipsel, powerpc, s390, s390x, sparc
> > >  dmraid | 1.0.0.rc16-4.2 | jessie  | source, amd64, armel, armhf, i386, 
> > > ia64, mips, mipsel, powerpc, s390, s390x, sparc
> > >  dmraid | 1.0.0.rc16-4.2 | sid     | source, amd64, armel, armhf, i386, 
> > > ia64, mips, mipsel, powerpc, s390, s390x, sparc
> > > 
> > > Also Debian only has lvm2 (note the 2 in the package name) version 
> > > 2.02.98-1
> > > 
> > > $ rmadison lvm2
> > >  lvm2 | 2.02.66-5 | squeeze | source, amd64, armel, i386, ia64, mips, 
> > > mipsel, powerpc, s390, sparc
> > >  lvm2 | 2.02.95-7 | wheezy  | source, amd64, armel, armhf, i386, ia64, 
> > > mips, mipsel, powerpc, s390, s390x, sparc
> > >  lvm2 | 2.02.95-7 | jessie  | source, amd64, armel, armhf, i386, ia64, 
> > > mips, mipsel, powerpc, s390, s390x, sparc
> > >  lvm2 | 2.02.98-1 | sid     | source, amd64, armel, armhf, i386, ia64, 
> > > mips, mipsel, powerpc, s390, s390x, sparc
> > > 
> > > My guess is you have some non-Debian repositories in your sources.list. 
> > > Please try to reproduce this bug with Debian packages and reopen this 
> > > bug and assign to the correct package.
> > > 
> > > Kind regards,
> > > Andrei
> > 
> 



-- 
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)

Attachment: signature.asc
Description: Digital signature

Reply via email to