The what should be updated in -current thread

Originally Posted by ttk Robby, I've often wondered, do you have scripts you like to use for testing Slackware? Or do you exercise individual packages by hand and look around for signs of trouble?

No scripts :-)

If it passes the "works for me" test and there aren't any obvious issues, it gets queued up. Sometimes it fails the "works for volkerdi" test or the "works for some other team member" test, and so we regroup and take another look :-)

Originally Posted by ivandi nfs-utils >= 1.3.0 wont compile on current with nfs4 and krb5 support. Looks like keyutils is too old. If you are going to upgrade nfs-utils could you look at keyutils too. keyutils-1.5.5 > 1.5.9

Got it; thanks! Do you use nfs4 (I'm guessing you rebuild nfs-utils then??) I'd love to see a writeup on the slackdocs wiki about nfs4...

---------- Post added Dec 23rd, 2014 at 13:17 ----------

Originally Posted by ReaperX7 All the alsa related packages are now at version 1.0.28 with the exception of pyalsa-1.0.26. http://www.alsa-project.org/main/index.php/Main_Page

Yep, I've got the alsa stuff already; thanks!

Robby do you have a listing of all packages in -current with the upgrade availability list compared so we can deduce down anything else left?

By the way, why is that Doxygen is at 1.8.5 (release date 23-08-2013).
When I tried to build weston or libinput (don't remember really) there were some warnings about missing flags (as in not supported) from doxygen.
On latest version warnings were gone. Perhaps latest version (1.8.8) should be tested and added?

[QUOTE=rworkman;5289668]Done, but I haven't used wicd in quite some time, so I'd like someone to confirm that these work.../QUOTE]

Robby thanks for the upgrade on wicd,

Here is some feedbacks on my machine (slackware64-current with xfce4 as window manager, no KDE4 stuff whatsoever).

The wicd icon is not displayed in the taskbar (I've got a white/blank icon with a red cross in It) but the GTK interface works.
The "curses" interface (in a terminal) wouldn't start.

A basic test would be to launch wicd in a terminal like this:

$ wicd-curses

I tested with urwid-1.0.2, urwid-1.1.2, urwid-1.2.2, with all these releases I could use wicd in a terminal, nonetheless only urwid-1.0.2 works properly, with the others wicd display errors on quitting like these:

ERROR:dbus.connection:Exception in handler for D-Bus signal:
Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/dbus/connection.py", line 230, in maybe_handle_message
    self._handler(*args, **kwargs)
  File "/usr/share/wicd/curses/wicd-curses.py", line 97, in wrapper
    return func(*args, **kargs)
  File "/usr/share/wicd/curses/wicd-curses.py", line 850, in update_netlist
    self.wiredCB.get_body().set_list(wiredL)
  File "/usr/share/wicd/curses/wicd-curses.py", line 469, in set_list
    wired.ReadWiredNetworkProfile(self.get_selected_profile())
  File "/usr/share/wicd/curses/wicd-curses.py", line 535, in get_selected_profile
    return self.theList[loc]
IndexError: list index out of range

Originally Posted by ReaperX7 Robby do you have a listing of all packages in -current with the upgrade availability list compared so we can deduce down anything else left?

ConsoleKit2/
NetworkManager/
Thunar/
acl/
acpid/
adwaita-icon-theme/
alsa-lib/
alsa-oss/
alsa-utils/
at-spi2-atk/
at-spi2-core/
atk/
attr/
audacious/
audacious-plugins/
bison/
blueman/
bluez/
bluez-hcidump/
cdrtools/
cmake/
coreutils/
cryptsetup/
cups-2.x/
curl/
dbus/
dbus-glib/
dconf/
desktop-file-utils/
dhcp/
dhcpcd/
doxygen/
e2fsprogs/
fetchmail/
file/
flex/
freetype/
fuse/
gcr/
gdk-pixbuf2/
geeqie/
gettext/
ghostscript/
git/
glade3/
glib-networking/
glib2/
gmime/
gnome-icon-theme/
gnome-keyring/
gnome-themes-standard/
gnupg2/
gobject-introspection/
gpa/
gpgme/
gphoto2/
grub/
gsettings-desktop-schemas/
gtk+2/
gtk+3/
gucharmap/
guile/
gvfs/
harfbuzz/
hicolor-icon-theme/
iproute2/
iptables/
irssi/
iso-codes/
itstool/
kbd/
keyutils/
kmod/
less/
lftp/
libassuan/
libelf/
libevdev/
libgcrypt/
libgnome-keyring/
libgpg-error/
libgphoto2/
libgsf/
libksba/
libmtp/
libndp/
libnewt/
libnl3/
libnotify/
librsvg/
libsecret/
libsoup/
libssh/
libtool/
list
lvm2/
lzip/
man-pages/
mercurial/
netkit-ftp/
network-manager-applet/
nfs-utils/
nmap/
npth/
ntfs-3g/
obexd/
orage/
p11-kit/
pam/
pango/
patch/
pinentry/
poppler/
poppler-data/
ppp/
proftpd/
python/
rcs/
rdesktop/
readline/
reiserfsprogs/
shared-mime-info/
slrn/
smartmontools/
sysklogd/
sysvinit-scripts/
tar/
texinfo/
tmux/
tumbler/
udev/
udisks/
ulogd/
upower/
urwid/
util-linux/
wget/
wicd/
windowmaker/
wpa_supplicant/
x11/
xdg-utils/
xfce4-mixer/
xfce4-panel/
xfce4-power-manager/
xfce4-systemload-plugin/
xfce4-taskmanager/
xfce4-terminal/
xfdesktop/
xfsprogs/
xterm/
xz/

---------- Post added Dec 23rd, 2014 at 15:47 ----------

Originally Posted by heiser891 By the way, why is that Doxygen is at 1.8.5 (release date 23-08-2013). When I tried to build weston or libinput (don't remember really) there were some warnings about missing flags (as in not supported) from doxygen. On latest version warnings were gone. Perhaps latest version (1.8.8) should be tested and added?

I've got latest doxygen in the queue.

Originally Posted by _gin Originally Posted by rworkman Done, but I haven't used wicd in quite some time, so I'd like someone to confirm that these work... Robby thanks for the upgrade on wicd, Here is some feedbacks on my machine (slackware64-current with xfce4 as window manager, no KDE4 stuff whatsoever). The wicd icon is not displayed in the taskbar (I've got a white/blank icon with a red cross in It) but the GTK interface works.

I can't reproduce this - what you're seeing is the gtk stock "not found" icon. Is there someplace to declare a custom icon, and if so, do you have anything there? If not, see if you can find any icon mention in wicd's config directories (user-specific maybe) - we had a similar issue in upstream blueman after they did a similar change wrt using themed icons.

The "curses" interface (in a terminal) wouldn't start. A basic test would be to launch wicd in a terminal like this: $ wicd-curses I tested with urwid-1.0.2, urwid-1.1.2, urwid-1.2.2, with all these releases I could use wicd in a terminal, nonetheless only urwid-1.0.2 works properly, with the others wicd display errors on quitting like these: ERROR:dbus.connection:Exception in handler for D-Bus signal: Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/dbus/connection.py", line 230, in maybe_handle_message self._handler(*args, **kwargs) File "/usr/share/wicd/curses/wicd-curses.py", line 97, in wrapper return func(*args, **kargs) File "/usr/share/wicd/curses/wicd-curses.py", line 850, in update_netlist self.wiredCB.get_body().set_list(wiredL) File "/usr/share/wicd/curses/wicd-curses.py", line 469, in set_list wired.ReadWiredNetworkProfile(self.get_selected_profile()) File "/usr/share/wicd/curses/wicd-curses.py", line 535, in get_selected_profile return self.theList[loc] IndexError: list index out of range

Well, as far as I'm concerned, we'll just stay with 1.0.2 then.

@Robby: thanks for the list, very handy.

That leads to a question: should I understand that brltty (requested in post #46, build material proposed in post #98) won't be upgraded, is not ready, or that no decision has been made yet (at least by yourself)?

Oh, and IMHO that would deserve to be moved from /extra to /slackware{,64}.

Originally Posted by Didier Spaier @Robby: thanks for the list, very handy. That leads to a question: should I understand that brltty (requested in post #46, build material proposed in post #98) won't be upgraded, is not ready, or that no decision has been made yet (at least by yourself)? Oh, and IMHO that would deserve to be moved from /extra to /slackware{,64}.

I've never touched the brltty code, and I don't think now is a good time to start. I'm going to leave that for volkerdi, as he's always been the one to mess with that, and I like it that way :-)

Just because I don't have something in my queue is not at all an indication that it isn't queued elsewhere or won't be later; it simply means that *I* haven't done anything with it.

llvm-3.4.1 > 3.5.0 (for any and all sub-projects as well if needed for Slackware).

Originally Posted by ReaperX7 llvm-3.4.1 > 3.5.0 (for any and all sub-projects as well if needed for Slackware).

I think pprkut has that one.

Does Slackware use anything other than Clang from the LLVM project?

Hi Robby,

I tried out your updated wicd-1.7.3, it seems to work for me here (checked wicd-gtk and wicd-curses).

However when I upgraded urwid, wicd-curses did not start and I got-

$ wicd-curses 
Traceback (most recent call last):
  File "/usr/share/wicd/curses/wicd-curses.py", line 1307, in <module>
    main()
  File "/usr/share/wicd/curses/wicd-curses.py", line 1224, in main
    ui.run_wrapper(run)
  File "/usr/lib64/python2.7/site-packages/urwid/display_common.py", line 757, in run_wrapper
    return fn()
  File "/usr/share/wicd/curses/wicd-curses.py", line 97, in wrapper
    return func(*args, **kargs)
  File "/usr/share/wicd/curses/wicd-curses.py", line 1234, in run
    app = appGUI()
  File "/usr/share/wicd/curses/wicd-curses.py", line 754, in __init__
    self.update_status()
  File "/usr/share/wicd/curses/wicd-curses.py", line 97, in wrapper
    return func(*args, **kargs)
  File "/usr/share/wicd/curses/wicd-curses.py", line 924, in update_status
    self.set_status):
  File "/usr/share/wicd/curses/wicd-curses.py", line 97, in wrapper
    return func(*args, **kargs)
  File "/usr/share/wicd/curses/wicd-curses.py", line 177, in check_for_wireless
    ('$C', ip))
  File "/usr/share/wicd/curses/wicd-curses.py", line 974, in set_status
    self.update_ui()
  File "/usr/share/wicd/curses/wicd-curses.py", line 97, in wrapper
    return func(*args, **kargs)
  File "/usr/share/wicd/curses/wicd-curses.py", line 1156, in update_ui
    input_data = ui.get_input_nonblocking()
AttributeError: 'Screen' object has no attribute '

Offtopic:
xfce4-taskmanager has had an update-
https://mail.xfce.org/pipermail/xfce...er/000350.html

I tried gtk2 and gtk3 versions, both seem to work for me.

xf86-video-intel was upgraded to 2.99.917 a few days ago. This version works better for me than the previous pre-release versions. No more glitches in firefox and fbpanel.

[QUOTE=_gin;5289714]

Originally Posted by rworkman Done, but I haven't used wicd in quite some time, so I'd like someone to confirm that these work.../QUOTE] Robby thanks for the upgrade on wicd, Here is some feedbacks on my machine (slackware64-current with xfce4 as window manager, no KDE4 stuff whatsoever). The wicd icon is not displayed in the taskbar (I've got a white/blank icon with a red cross in It) but the GTK interface works. The "curses" interface (in a terminal) wouldn't start. A basic test would be to launch wicd in a terminal like this: $ wicd-curses I tested with urwid-1.0.2, urwid-1.1.2, urwid-1.2.2, with all these releases I could use wicd in a terminal, nonetheless only urwid-1.0.2 works properly, with the others wicd display errors on quitting like these: ERROR:dbus.connection:Exception in handler for D-Bus signal: Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/dbus/connection.py", line 230, in maybe_handle_message self._handler(*args, **kwargs) File "/usr/share/wicd/curses/wicd-curses.py", line 97, in wrapper return func(*args, **kargs) File "/usr/share/wicd/curses/wicd-curses.py", line 850, in update_netlist self.wiredCB.get_body().set_list(wiredL) File "/usr/share/wicd/curses/wicd-curses.py", line 469, in set_list wired.ReadWiredNetworkProfile(self.get_selected_profile()) File "/usr/share/wicd/curses/wicd-curses.py", line 535, in get_selected_profile return self.theList[loc] IndexError: list index out of range

I had some issues with wicd-curses from 1.7.x and urwid 1.3 on my manjaro install. There was a patch at archlinux: https://projects.archlinux.org/svnto...cd3f4343dbf2fd
There is an update of wicd just a few days and have not tried it.
1.7.x had no issues with urwid 1.2.x on my manjaro install.