maemo.org - Talk - Broken packages waiting for a maintainer or a deletion

maemo.org - Talk (https://talk.maemo.org/index.php)

- Applications (https://talk.maemo.org/forumdisplay.php?f=41)

- - Broken packages waiting for a maintainer or a deletion (https://talk.maemo.org/showthread.php?t=88353)

Broken packages waiting for a maintainer or a deletion

Update:
See the wiki page: http://en.wikipedia.org/wiki/Journey..._video_game%29

Old info:

Since this thread started collecting broken packages I've changed the title.
Please
a) try contacting maintainers and post results by updating the post where you mentioned the package as broken;
b) or just add that you don't want to so someone else would.

waiting for status:

minigpsd http://talk.maemo.org/showpost.php?p...57&postcount=9
wifi-switcher http://talk.maemo.org/showpost.php?p...2&postcount=10
maemoreactor simonknowsmaemo netmon http://talk.maemo.org/showpost.php?p...7&postcount=15

a)

b)

meld (one of my favourite tools! :( ) http://talk.maemo.org/showpost.php?p...0&postcount=13
pc-connectivity-manager see below

Code:

$ sudo apt-get autoremove --purge

...

The following packages will be REMOVED:

  openssh* pc-connectivity-manager* rdesktop-cli* sbrshd* sshfs* udhcpd* unfs3* x11vnc*

...

Removing openssh ...

Removing pc-connectivity-manager ...

### BEGIN Network Manager configuratio

### END Network Manager configuratio

Restoring /etc/network/interfaces

sed: /etc/bluetooth/mai: No such file or directory

sed: .co: No such file or directory

sed: f: No such file or directory

mv: cannot rename '/etc/bluetooth/mai': No such file or directory

mv: cannot rename '.co': No such file or directory

mv: cannot rename 'f.tmp': No such file or directory

mv: cannot rename '/etc/bluetooth/mai': No such file or directory

mv: cannot rename '.co': No such file or directory

Purging configuration files for pc-connectivity-manager ...

sed: /etc/bluetooth/mai: No such file or directory

sed: .co: No such file or directory

sed: f: No such file or directory

mv: cannot rename '/etc/bluetooth/mai': No such file or directory

mv: cannot rename '.co': No such file or directory

mv: cannot rename 'f.tmp': No such file or directory

mv: cannot rename '/etc/bluetooth/mai': No such file or directory

mv: cannot rename '.co': No such file or directory

...

Re: Removing pc-connectivity-manager

What is your question?

I do not get it. Here are my questions:
Why did you say 'Yes' to this list?
Which of the packages listed would you want to get rid of?

Re: Removing pc-connectivity-manager

Quote:

Originally Posted by michaaa62 (Post 1306819)

What is your question?

I do not get it. Here are my questions:
Why did you say 'Yes' to this list?
Which of the packages listed would you want to get rid of?

I wanted to point that it looks like there are some errors in postrm script. Yes, I wanted to get rid of them all. I'm trying to figure out why does hildon-status-menu not starting properly, thus removing everything at least related to applets in it.

Re: Removing pc-connectivity-manager

Quote:

Originally Posted by int_ua (Post 1306828)

I wanted to point that it looks like there is a very poorly written postrm script.

Source of the latest Devel version 0.7.14
postrm

Code:

#!/bin/sh



# Check the os version

SDK_VERSION=`dpkg -s libhildon1 | grep Version | cut -d: -f2`

if test "x$SDK_VERSION" = "x 2.0.6-1"; then 

    DIABLO=1

    FREMANTLE=0

else

    DIABLO=0

    FREMANTLE=1

fi



IFACES="/etc/network/interfaces"

IFACES_TMP="/tmp/interfaces.tmp"

START="### BEGIN Network Manager"

END="### END Network Manager"

NM_CONFIG_STUFF=0

IFS=$'\n'



if [ "$1" = "remove" ]; then

    

    rm -f "${IFACES_TMP}"

    while read LINE; do



        echo "${LINE}" | grep "${START}" -

        if [ $? = 0 ]; then

            NM_CONFIG_STUFF=1

        fi



        if [ ${NM_CONFIG_STUFF} = 0 ]; then

            echo "${LINE}" >> "${IFACES_TMP}"

        fi



        echo "${LINE}" | grep "${END}" -

        if [ $? = 0 ]; then

            NM_CONFIG_STUFF=0

        fi

    done <${IFACES}



    if [ -f "${IFACES_TMP}" ]; then

        echo "Restoring ${IFACES}"

        cp -f "${IFACES_TMP}" "${IFACES}"

        rm -f "${IFACES_TMP}"

    fi

fi



if test $FREMANTLE -eq 1 ; then

    # echo "Removing from Fremantle device"



    #disable network plugin

    BLUEZ_CONF="/etc/bluetooth/main.conf"



    sed -e "s/^#DisablePlugins/DisablePlugins/g" ${BLUEZ_CONF} > ${BLUEZ_CONF}.tmp

    mv ${BLUEZ_CONF}.tmp ${BLUEZ_CONF}

    # /etc/init.d/bluetooth restart

fi



exit 0

Re: Some errors in postrm script of pc-connectivity-manager that look dangerous

Code:

IFS=$'\n'

gotcha

Code:

IFS=$(echo -e "\n")

Re: Some errors in postrm script of pc-connectivity-manager that look dangerous

Quote:

Originally Posted by int_ua (Post 1306897)

Code:

IFS=$'\n'

gotcha

Code:

IFS=$(echo -e "\n")

Has this been reported to maintainers?

Re: Some errors in postrm script of pc-connectivity-manager that look dangerous

Quote:

Originally Posted by sixwheeledbeast (Post 1306939)

Has this been reported to maintainers?

reporting...

They've disabled receiving private messagges. I'm not in a mood to hunt them on google, anyone else want to try?

Re: Some errors in postrm script of pc-connectivity-manager that look dangerous

Quote:

Originally Posted by int_ua (Post 1306985)

reporting...

They've disabled receiving private messagges. I'm not in a mood to hunt them on google, anyone else want to try?

The package hasn't been maintained since 2009.
There's no bugtracker and no bugzilla.

Should be an easy fix if its worth bothering but I don't want to attempt to fix a DOA package, I wouldn't use.

However from a quick search there maybe other bugs

http://talk.maemo.org/showpost.php?p...3&postcount=13

Does anybody use it successfully on PR1.3.1/CSSU?

Should the package just be removed from the Repos as broken?

Last changelog file

Code:

pc-connectivity-manager (0.7.14) experimental; urgency=low



  * Bug that prevents sbrsh applet to use wildcards fixed 



 -- Walter Guerra <walter.guerra(no_spam)@(no_spam)signove(no_spam).com>  

Tue, 24 Nov 2009 18:45:45 -0300

Re: Some errors in postrm script of pc-connectivity-manager that look dangerous

Quote:

Originally Posted by sixwheeledbeast (Post 1307033)

The package hasn't been maintained since 2009.
There's no bugtracker and no bugzilla.....

... .However from a quick search there maybe other bugs

Does anybody use it successfully on PR1.3.1/CSSU?

Should the package just be removed from the Repos as broken?
[/code]

I remember trying this on PR1.2 and it was not working back then. Yes it should be pulled from the repos (maybe an archive repo) and so prolly should some other non-working packages eg. minigpsd.

Re: Some errors in postrm script of pc-connectivity-manager that look dangerous

Quote:

Originally Posted by handaxe (Post 1307057)

I remember trying this on PR1.2 and it was not working back then. Yes it should be pulled from the repos (maybe an archive repo) and so prolly should some other non-working packages eg. minigpsd.

IMO rather than pulling things into a separate repo, I would just remove/move the deb from the repo and leave the source in garage.

This way they may get repaired in the future but are un-installable to people that cannot fix them (people without scratchbox etc).

As an idea, if when things are deemed unstable and pulled from the repos maybe a warning could be send out on updating CSSU or whatever. Some users may have "stable-unstable" packages with no easy way of telling them. If not on TMO.

wifi-switcher is another broken package I believe.

In addition @int_ua what was that package you found with the broken QSettings? Did that get repaired?