reflum,

On Mon, 2011-01-03 at 11:41 -0700, Bob Proulx wrote:
> Philipp Schafft wrote:
> > I just tested it in my sid sandbox and it worked fine.
> >=20
> > The current postrm script does the following:
> >         purge)
> >                 if getent passwd|grep -q ^muroard: ; then
> >                         userdel muroard 2>&1 > /dev/null || true
> >                 fi
> >=20
> > I don't see how it could leave the user beside userdel failing.
> 
> Hmm...  Agreed.  If that is there then it should have been removed.
> 
> Here is what I know:
> 
>   The following NEW packages will be installed:
>     dnet-common libdnet libroar0 muroard
>   The following packages will be upgraded:
>     ... ices2 ...
>   17 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.

Seems this way:
ices2 depends libroar0.
libroar0 recommends roaraudio-server which is virtual, muroard got
selected.
libroar0 depends libdnet.
libdnet recommends dnet-common.


> And so those were installed with the ices2 upgrade this morning.  This
> caused the hardware ethernet address to be set to aa:0:4:0:a:4.
> I filed Bug#608807 concerning it.

Will answer to that after I answered to this one.


> To restore functionality I removed the following:
> 
>   $ sudo apt-get remove --purge dnet-common libdnet libroar0 muroard
>   Reading package lists... Done
>   Building dependency tree      =20
>   Reading state information... Done
>   The following packages will be REMOVED:
>     dnet-common* ices2* libdnet* libroar0* muroard*
>   0 upgraded, 0 newly installed, 5 to remove and 0 not upgraded.
>   After this operation, 1,200 kB disk space will be freed.
>   Do you want to continue [Y/n]?=20
>   (Reading database ... 282207 files and directories currently
> installed.)
>   Removing dnet-common ...
>   Purging configuration files for dnet-common ...
>   Removing ices2 ...
>   Removing libroar0 ...
>   Purging configuration files for libroar0 ...
>   Removing libdnet ...
>   Purging configuration files for libdnet ...
>   Removing muroard ...
>   Stopping muRoarD: muroard.
>   Purging configuration files for muroard ...
>   userdel: user muroard is currently logged in
>   Processing triggers for man-db ...
>   Processing triggers for doc-base ...
>   Processing 1 removed doc-base file(s)...
>   Registering documents with scrollkeeper...
> 
> But it didn't clean up everything:
> 
>   # grep muroard /etc/passwd
>   muroard:x:125:29::/var/lib/muroard:/bin/false
> 
> Therefore I removed the user manually.
> 
>   # deluser muroard
>   Removing user `muroard' ...
>   Done.
> 
> > Please do the following:
> >  # userdel muroard; echo $?
> > and report the output.
> 
> Too late since I already removed the user manually.  But clearly in
> the above output the user did exist at that time and was removed by
> the deluser command.  If I run it again now it clearly has produces
> different output ensuring that we can trust that the above actually
> did remove the user.
> 
>   # deluser muroard
>   /usr/sbin/deluser: The user `muroard' does not exist.

hm. Still after both Patrick Matthäi and me had a look at the package we
can not reproduce or find by audit the error.

Can you please try installing and purging again? if you only install
muroard there should be no problem with *dnet* as it is a depends of
libroar0 not muroard.


> Unfortunately due to Bug#608807 I am hesitant to install it again to
> try it because I don't want decnet to reset my mac address again.  I
> could however create a dummy package to fulfil the dependency for
> testing if needed.

See above.

-- 
Philipp.
 (Rah of PH2)

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to