Requests for -current (14.2-->15.0)

willysr · 03-23-2020, 08:16 PM

Quote:

Originally Posted by drgibbon

curl-7.69.1-x86_64-2.txz causes breakage with git on my system:

Code:

git clone https://gitlab.com/SlackBuilds.org/slackbuilds.git
Cloning into 'slackbuilds'...
fatal: unable to access 'https://gitlab.com/SlackBuilds.org/slackbuilds.git/': error setting certificate verify locations:
  CAfile: /usr/share/curl/ca-bundle.crt
  CApath: /etc/ssl/certs

Reverting to curl-7.69.1-x86_64-1.txz fixes it.

confirmed here as well

redneonglow · 03-23-2020, 09:19 PM

Quote:

Originally Posted by willysr

confirmed here as well

Same here, I get similar git errors when trying to use sbotools

willysr · 03-23-2020, 09:40 PM

removing

Code:

--with-ca-bundle=/usr/share/curl/ca-bundle.crt \

and rebuilding it fixed the issue, but i'm not sure if that's the perfect solution.

sombragris · 03-23-2020, 09:52 PM

Code:

xap/audacious-4.0-x86_64-2.txz: Rebuilt.
       Rebuilt with autotools to fix French language support. Thanks to gmgf.
xap/audacious-plugins-4.0-x86_64-2.txz: Rebuilt.
       Rebuilt with autotools.

In my system, updating to the rebuilt audacious gave me no UI. The executable was there but the window whas nowhere to be seen
I had to explicitly activate it using "audacious -m", but all my UI customizations were lost.

willysr · 03-23-2020, 10:24 PM

it's working fine here with audacious. It loads the new Qt-based UI

gmgf · 03-24-2020, 12:42 AM

Quote:

Originally Posted by willysr

it's working fine here with audacious. It loads the new Qt-based UI

same here, no problem.

drgibbon · 03-24-2020, 02:05 AM

The new curl-7.69.1-x86_64-3.txz build fixes it, thanks Pat!

mats_b_tegner · 03-24-2020, 05:11 PM

LLVM 10.0.0 is finally out:
https://lists.llvm.org/pipermail/llv...ch/000087.html
https://releases.llvm.org/download.html#10.0.0
Edit:
LLVM/Clang 10.0.0 etc. has been added to -current now.

AlexSlack · 03-24-2020, 10:24 PM

Quote:

Originally Posted by sombragris

Code:

xap/audacious-4.0-x86_64-2.txz: Rebuilt.
       Rebuilt with autotools to fix French language support. Thanks to gmgf.
xap/audacious-plugins-4.0-x86_64-2.txz: Rebuilt.
       Rebuilt with autotools.

In my system, updating to the rebuilt audacious gave me no UI. The executable was there but the window whas nowhere to be seen
I had to explicitly activate it using "audacious -m", but all my UI customizations were lost.

It seems that some configurations are lost, it usually happens when there is a major update, I usually lost my Winamp interface setup.
The new version is missing the AOSD plugin (not critical) and the Winamp interface does not allow me to drop files, it seems that users of the Winamp interface will need to rebuild with gtk2 as suggested in the release notes or wait the port is completed

.

Code:

Users of the Winamp-like UI may want to continue using GTK2 for now.

Note:
I rebuilt the audacious and audacious-plugins packages with autotools and the option --enable-gtk, you can have both Qt and Gtk installed, in order to use Gtk2 interface you can use the -G switch. The old Gtk configuration was lost in my case but once setup again is not lost on the change of interfaces.

Hope this helps.

Paulo2 · 03-24-2020, 11:40 PM

Quote:

Originally Posted by AlexSlack

It seems that some configurations are lost, it usually happens when there is a major update, I usually lost my Winamp interface setup.
The new version is missing the AOSD plugin (not critical) and the Winamp interface does not allow me to drop files, it seems that users of the Winamp interface will need to rebuild with gtk2 as suggested in the release notes or wait the port is completed

.

Code:

Users of the Winamp-like UI may want to continue using GTK2 for now.

Note:
I rebuilt the audacious and audacious-plugins packages with autotools and the option --enable-gtk, you can have both Qt and Gtk installed, in order to use Gtk2 interface you can use the -G switch. The old Gtk configuration was lost in my case but once setup again is not lost on the change of interfaces.

Hope this helps.

It helped, thanks

saxa · 03-25-2020, 09:18 AM

Are there any special reasons why not to use the latest ?

libsigc++-3.0.3
https://download.gnome.org/sources/l...+-3.0.3.tar.xz

gmgf · 03-25-2020, 12:32 PM

Same question that "saxa" for pango:
(Are there any special reasons why not to use the latest ?)

http://ftp.gnome.org/pub/gnome/sourc...-1.44.7.tar.xz

linuxtinker · 03-25-2020, 12:41 PM

Quote:

Mon Mar 23 20:03:39 UTC 2020
a/e2fsprogs-1.45.6-x86_64-1.txz: Upgraded.

I notice this update removed :

fname_encoding = utf8 from the make2fs.conf options .

Are we sticking with this now?

thx

volkerdi · 03-25-2020, 02:32 PM

Quote:

Originally Posted by linuxtinker

I notice this update removed :

fname_encoding = utf8 from the make2fs.conf options .

Are we sticking with this now?

thx

That change came from upstream and I can't find any information about it. Perhaps it's the default now?

linuxtinker · 03-25-2020, 03:35 PM

Quote:

Originally Posted by linuxtinker

I notice this update removed :

fname_encoding = utf8 from the make2fs.conf options .

Are we sticking with this now?

thx

Quote:

Originally Posted by volkerdi

That change came from upstream and I can't find any information about it. Perhaps it's the default now?

After some digging around it seems to not be an option anymore ( not in man page). Might have something to do with the built-in casefold feature being enabled., the mailing list was giving me a headache so guess I'll just have to trust upstream .

Sorry for the noise and thanks for checking into it.