Development March 2021

development@lists.ipfire.org

14 participants
107 discussions

[PATCH] GUI: Periodically reload RRD graphs
by Leo-Andres Hofmann 18 Mar '21

18 Mar '21

The RRD graphs are embedded in an iframe tag. Therefore it is possible to refresh them periodically without reloading or changing the pages. This patch adds a graph reload javascript to the ipfire main theme. Signed-off-by: Leo-Andres Hofmann <hofmann(a)leo-andres.de> --- Hi, This is more of a nice-to-have, an idea I would like to present. As I was working on the QoS graphs, I noticed that all RRD graphs are embedded in an iframe. I wrote a little javascript that periodically reloads these graphs. The refresh interval is based on the graph's time range, i.e. hourly graphs are refreshed more often. Reloading should stop in case of a network error, but I haven't fully tested this yet. This patch adds a checkbox to the GUI settings (default: disabled), translations, ... If you just want to try the javascript, you can simply paste it to the html <head> in html/themes/ipfire/include/functions.pl. Be sure to escape the '$' then. Best regards Leo doc/language_issues.en | 1 + doc/language_issues.es | 1 + doc/language_issues.fr | 1 + doc/language_issues.it | 1 + doc/language_issues.nl | 1 + doc/language_issues.pl | 1 + doc/language_issues.ru | 1 + doc/language_issues.tr | 1 + doc/language_missings | 7 ++ html/cgi-bin/gui.cgi | 16 ++++ html/html/themes/ipfire/include/functions.pl | 7 ++ .../themes/ipfire/include/js/reloadGraphs.js | 81 +++++++++++++++++++ langs/de/cgi-bin/de.pl | 1 + langs/en/cgi-bin/en.pl | 1 + 14 files changed, 121 insertions(+) create mode 100644 html/html/themes/ipfire/include/js/reloadGraphs.js diff --git a/doc/language_issues.en b/doc/language_issues.en index 7819541c2..9edc57d19 100644 --- a/doc/language_issues.en +++ b/doc/language_issues.en @@ -1446,6 +1446,7 @@ WARNING: untranslated string: password not set = Password not set. WARNING: untranslated string: password too short = Password is too short. WARNING: untranslated string: passwords do not match = Passwords do not match. WARNING: untranslated string: percentage = Percentage +WARNING: untranslated string: periodically reload graphs = Periodically refresh RRD graphs WARNING: untranslated string: persistent = Persistent WARNING: untranslated string: pfs yes no = Perfect Forward Secrecy (PFS) WARNING: untranslated string: pkcs12 file password = PKCS12 File Password diff --git a/doc/language_issues.es b/doc/language_issues.es index 952321fbe..3d623302c 100644 --- a/doc/language_issues.es +++ b/doc/language_issues.es @@ -1318,6 +1318,7 @@ WARNING: untranslated string: pakfire tree = Repository WARNING: untranslated string: pakfire tree stable = Stable WARNING: untranslated string: pakfire tree testing = Testing WARNING: untranslated string: pakfire tree unstable = Unstable +WARNING: untranslated string: periodically reload graphs = Periodically refresh RRD graphs WARNING: untranslated string: please reboot to apply your changes = Please reboot to apply your changes WARNING: untranslated string: pptp netconfig = My Net Config WARNING: untranslated string: pptp peer = Peer diff --git a/doc/language_issues.fr b/doc/language_issues.fr index 9fe5ca21c..e3a38df4e 100644 --- a/doc/language_issues.fr +++ b/doc/language_issues.fr @@ -914,6 +914,7 @@ WARNING: untranslated string: guardian logtarget_syslog = unknown string WARNING: untranslated string: guardian no entries = unknown string WARNING: untranslated string: guardian service = unknown string WARNING: untranslated string: pakfire ago = ago. +WARNING: untranslated string: periodically reload graphs = Periodically refresh RRD graphs WARNING: untranslated string: route config changed = unknown string WARNING: untranslated string: routing config added = unknown string WARNING: untranslated string: routing config changed = unknown string diff --git a/doc/language_issues.it b/doc/language_issues.it index 29c9c7d58..a66c693b0 100644 --- a/doc/language_issues.it +++ b/doc/language_issues.it @@ -1108,6 +1108,7 @@ WARNING: untranslated string: pakfire tree = Repository WARNING: untranslated string: pakfire tree stable = Stable WARNING: untranslated string: pakfire tree testing = Testing WARNING: untranslated string: pakfire tree unstable = Unstable +WARNING: untranslated string: periodically reload graphs = Periodically refresh RRD graphs WARNING: untranslated string: please reboot to apply your changes = Please reboot to apply your changes WARNING: untranslated string: pptp netconfig = My Net Config WARNING: untranslated string: pptp peer = Peer diff --git a/doc/language_issues.nl b/doc/language_issues.nl index d6cad0dee..a2b978ccc 100644 --- a/doc/language_issues.nl +++ b/doc/language_issues.nl @@ -1140,6 +1140,7 @@ WARNING: untranslated string: pakfire tree = Repository WARNING: untranslated string: pakfire tree stable = Stable WARNING: untranslated string: pakfire tree testing = Testing WARNING: untranslated string: pakfire tree unstable = Unstable +WARNING: untranslated string: periodically reload graphs = Periodically refresh RRD graphs WARNING: untranslated string: please reboot to apply your changes = Please reboot to apply your changes WARNING: untranslated string: pptp netconfig = My Net Config WARNING: untranslated string: pptp peer = Peer diff --git a/doc/language_issues.pl b/doc/language_issues.pl index b8fba938f..7f2b72cc0 100644 --- a/doc/language_issues.pl +++ b/doc/language_issues.pl @@ -1327,6 +1327,7 @@ WARNING: untranslated string: pakfire tree = Repository WARNING: untranslated string: pakfire tree stable = Stable WARNING: untranslated string: pakfire tree testing = Testing WARNING: untranslated string: pakfire tree unstable = Unstable +WARNING: untranslated string: periodically reload graphs = Periodically refresh RRD graphs WARNING: untranslated string: please reboot to apply your changes = Please reboot to apply your changes WARNING: untranslated string: pptp netconfig = My Net Config WARNING: untranslated string: pptp peer = Peer diff --git a/doc/language_issues.ru b/doc/language_issues.ru index d507911f1..f988580cf 100644 --- a/doc/language_issues.ru +++ b/doc/language_issues.ru @@ -1322,6 +1322,7 @@ WARNING: untranslated string: pakfire tree = Repository WARNING: untranslated string: pakfire tree stable = Stable WARNING: untranslated string: pakfire tree testing = Testing WARNING: untranslated string: pakfire tree unstable = Unstable +WARNING: untranslated string: periodically reload graphs = Periodically refresh RRD graphs WARNING: untranslated string: please reboot to apply your changes = Please reboot to apply your changes WARNING: untranslated string: pptp netconfig = My Net Config WARNING: untranslated string: pptp peer = Peer diff --git a/doc/language_issues.tr b/doc/language_issues.tr index 04343d527..dc0fd98f0 100644 --- a/doc/language_issues.tr +++ b/doc/language_issues.tr @@ -1021,6 +1021,7 @@ WARNING: untranslated string: pakfire tree = Repository WARNING: untranslated string: pakfire tree stable = Stable WARNING: untranslated string: pakfire tree testing = Testing WARNING: untranslated string: pakfire tree unstable = Unstable +WARNING: untranslated string: periodically reload graphs = Periodically refresh RRD graphs WARNING: untranslated string: please reboot to apply your changes = Please reboot to apply your changes WARNING: untranslated string: processor vulnerability mitigations = Processor Vulnerability Mitigations WARNING: untranslated string: ptr = PTR diff --git a/doc/language_missings b/doc/language_missings index f10c4f242..89808f3b5 100644 --- a/doc/language_missings +++ b/doc/language_missings @@ -669,6 +669,7 @@ < pakfire tree stable < pakfire tree testing < pakfire tree unstable +< periodically reload graphs < please reboot to apply your changes < pptp netconfig < pptp peer @@ -922,6 +923,7 @@ < dhcp valid range required when deny known clients checked < g.dtm < g.lite +< periodically reload graphs < token < token not set < upload fcdsl.o @@ -1198,6 +1200,7 @@ < pakfire tree stable < pakfire tree testing < pakfire tree unstable +< periodically reload graphs < please reboot to apply your changes < pptp netconfig < pptp peer @@ -1632,6 +1635,7 @@ < pakfire tree stable < pakfire tree testing < pakfire tree unstable +< periodically reload graphs < please reboot to apply your changes < pptp netconfig < pptp peer @@ -2407,6 +2411,7 @@ < pakfire tree stable < pakfire tree testing < pakfire tree unstable +< periodically reload graphs < please reboot to apply your changes < pptp netconfig < pptp peer @@ -3297,6 +3302,7 @@ < pakfire tree stable < pakfire tree testing < pakfire tree unstable +< periodically reload graphs < please reboot to apply your changes < pptp netconfig < pptp peer @@ -3660,6 +3666,7 @@ < pakfire tree stable < pakfire tree testing < pakfire tree unstable +< periodically reload graphs < please reboot to apply your changes < processor vulnerability mitigations < ptr diff --git a/html/cgi-bin/gui.cgi b/html/cgi-bin/gui.cgi index f06b0f923..a5255dbce 100644 --- a/html/cgi-bin/gui.cgi +++ b/html/cgi-bin/gui.cgi @@ -37,6 +37,7 @@ my $errormessage=''; $cgiparams{'SPEED'} = 'off'; +$cgiparams{'RELOADGRAPHS'} = 'off'; $cgiparams{'WINDOWWITHHOSTNAME'} = 'off'; $cgiparams{'REFRESHINDEX'} = 'off'; $cgiparams{'ACTION'} = ''; @@ -88,6 +89,7 @@ if ($cgiparams{'ACTION'} eq "$Lang::tr{'save'}") $mainsettings{'WINDOWWITHHOSTNAME'} = $cgiparams{'WINDOWWITHHOSTNAME'}; $mainsettings{'PPPUPDOWNBEEP'} = $cgiparams{'PPPUPDOWNBEEP'}; $mainsettings{'SPEED'} = $cgiparams{'SPEED'}; + $mainsettings{'RELOADGRAPHS'} = $cgiparams{'RELOADGRAPHS'}; $mainsettings{'THEME'} = $cgiparams{'theme'}; $mainsettings{'REFRESHINDEX'} = $cgiparams{'REFRESHINDEX'}; &General::writehash("${General::swroot}/main/settings", \%mainsettings); @@ -125,6 +127,11 @@ if ($cgiparams{'ACTION'} eq "$Lang::tr{'save'}") # by manually setting the var to off $cgiparams{'SPEED'} = 'on'; } + if($mainsettings{'RELOADGRAPHS'}) { + $cgiparams{'RELOADGRAPHS'} = $mainsettings{'RELOADGRAPHS'}; + } else { + $cgiparams{'RELOADGRAPHS'} = 'off'; + } } # Default settings @@ -134,6 +141,7 @@ if ($cgiparams{'ACTION'} eq "$Lang::tr{'restore defaults'}") $cgiparams{'PPPUPDOWNBEEP'} = 'on'; $cgiparams{'REFRESHINDEX'} = 'off'; $cgiparams{'SPEED'} = 'on'; + $cgiparams{'RELOADGRAPHS'} = 'off'; $cgiparams{'THEME'} = 'ipfire'; } @@ -153,6 +161,10 @@ $checked{'SPEED'}{'off'} = ''; $checked{'SPEED'}{'on'} = ''; $checked{'SPEED'}{$cgiparams{'SPEED'}} = "checked='checked'"; +$checked{'RELOADGRAPHS'}{'off'} = ''; +$checked{'RELOADGRAPHS'}{'on'} = ''; +$checked{'RELOADGRAPHS'}{$cgiparams{'RELOADGRAPHS'}} = "checked='checked'"; + &Header::openpage($Lang::tr{'gui settings'}, 1, ''); &Header::openbigbox('100%', 'left', '', $errormessage); @@ -179,6 +191,10 @@ print <<END <td><input type='checkbox' name='SPEED' $checked{'SPEED'}{'on'} /></td> <td>$Lang::tr{'show ajax speedmeter in footer'}</td> </tr> +<tr> + <td><input type='checkbox' name='RELOADGRAPHS' $checked{'RELOADGRAPHS'}{'on'} /></td> + <td>$Lang::tr{'periodically reload graphs'}</td> +</tr> <tr> <td> </td> <td>$Lang::tr{'languagepurpose'}</td> diff --git a/html/html/themes/ipfire/include/functions.pl b/html/html/themes/ipfire/include/functions.pl index 9aec77497..7f3401119 100644 --- a/html/html/themes/ipfire/include/functions.pl +++ b/html/html/themes/ipfire/include/functions.pl @@ -147,6 +147,13 @@ END ; } +if ($settings{'RELOADGRAPHS'} eq 'on') { +print <<END + <script src="/themes/ipfire/include/js/reloadGraphs.js"></script> +END +; +} + print <<END </head> <body> diff --git a/html/html/themes/ipfire/include/js/reloadGraphs.js b/html/html/themes/ipfire/include/js/reloadGraphs.js new file mode 100644 index 000000000..c0c8bec9e --- /dev/null +++ b/html/html/themes/ipfire/include/js/reloadGraphs.js @@ -0,0 +1,81 @@ +/*############################################################################# +# # +# IPFire.org - A linux based firewall # +# Copyright (C) 2007-2021 IPFire Team <info(a)ipfire.org> # +# # +# This program is free software: you can redistribute it and/or modify # +# it under the terms of the GNU General Public License as published by # +# the Free Software Foundation, either version 3 of the License, or # +# (at your option) any later version. # +# # +# This program is distributed in the hope that it will be useful, # +# but WITHOUT ANY WARRANTY; without even the implied warranty of # +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # +# GNU General Public License for more details. # +# # +# You should have received a copy of the GNU General Public License # +# along with this program. If not, see <http://www.gnu.org/licenses/>. # +# # +#############################################################################*/ + +var graphs_reloadTimers = new Map(); + +//graph onload event: graph is now loaded, start reload timer +function graphs_onloadEvent(graphObj, startTimer = true) { + if(! graphObj) { + return; //graph iframe object is missing + } + + //get graph parameters from iframe url: [url]?[graph name]?[time range] + let url = graphObj.contentWindow.location.href; + if((! url) || (url === 'about:blank')) { + url = graphObj.src; + } + url = url.split('?', 3); + let graphRange = url.pop(); + let graphName = url.pop(); + + if((! graphName) || (! graphRange)) { + return; //url parameters are missing + } + + //clear pending reload timeout to prevent multiple timer starts + if(graphs_reloadTimers.has(graphName)) { + clearTimeout(graphs_reloadTimers.get(graphName)); + graphs_reloadTimers.delete(graphName); + } + + if(startTimer) { + //determine reload interval + let interval = 60; //default: 60s + if(graphRange === 'hour') { + interval = 10; + } else if(graphRange === 'month' || graphRange === 'year') { + interval = 180; + } + + //start timeout and store timer id + let timer = setTimeout(function(graphFrame, timerRef) { + graphs_reloadTimers.delete(timerRef); //clear expired timer + + //reload graph iframe, ignore cache + graphFrame.contentWindow.location.reload(true); + }, interval * 1000, graphObj, graphName); + graphs_reloadTimers.set(graphName, timer); + } +} + +//document.ready, must fire before iframes load +$(function() { + //attach onload event to graphs + $('iframe.graph').each(function() { + $(this).on({ + load: function() { + graphs_onloadEvent(this); + }, + error: function() { //stop reload on error + graphs_onloadEvent(this, false); + } + }); + }); +}); diff --git a/langs/de/cgi-bin/de.pl b/langs/de/cgi-bin/de.pl index b3c2a69da..00e6b9853 100644 --- a/langs/de/cgi-bin/de.pl +++ b/langs/de/cgi-bin/de.pl @@ -2007,6 +2007,7 @@ 'pc add' => 'PC hinzufügen', 'pdc options' => 'PDC Optionen', 'percentage' => 'Prozent', +'periodically reload graphs' => 'RRD Graphen periodisch neu laden', 'persistent' => 'Dauerhaft', 'pfs yes no' => 'Perfect Forward Secrecy (PFS)', 'phase1 group' => 'Phase1 Gruppe', diff --git a/langs/en/cgi-bin/en.pl b/langs/en/cgi-bin/en.pl index 9767be178..ed9e4996a 100644 --- a/langs/en/cgi-bin/en.pl +++ b/langs/en/cgi-bin/en.pl @@ -2037,6 +2037,7 @@ 'pc add' => 'Add workstation', 'pdc options' => 'PDC options', 'percentage' => 'Percentage', +'periodically reload graphs' => 'Periodically refresh RRD graphs', 'persistent' => 'Persistent', 'pfs yes no' => 'Perfect Forward Secrecy (PFS)', 'phase1 group' => 'Phase1 Group', -- 2.27.0.windows.1

6 13

Fwd: Feedback on Core Update 155 Testing
by Jonatan Schlag 18 Mar '21

18 Mar '21

Sorry for missing the list :-(. ————————- Hi Adolf, thanks for having an eye on the community and reporting things back. Arne has already fixed that (see https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=5d747ddb70e74c9f5503618… and other comments in the current master). Sorry for answering this so late. There was communication on this over different places (community, chat, here, ...) and so things get lost somehow. I do not know if this could be improved, but at least I want to say sorry that you were not aware that the problem was already fixed. Greetings Jonatan >>> Am 17.03.2021 um 13:40 schrieb Adolf Belka <adolf.belka(a)ipfire.org>: >>> >> Hi All, >> >>> On 17/03/2021 11:51, Adolf Belka wrote: >>> Hi Everyone, >>> >>>> On 17/03/2021 10:35, Adolf Belka wrote: >>>> Dear all, >>>> >>>> There is feedback on the forum about IPFire not rebooting after update and needing a soft reset. After that it boots again. I also found the same effect on my VM testbed system for testing. >>>> >>>> https://community.ipfire.org/t/feedback-core-update-155-testing/4896 >>>> >>>> That symptom triggered my memory (a bit late) and I found the discussion about my sysvinit patch. >>>> >>>> https://lists.ipfire.org/pipermail/development/2021-February/009403.html >>>> >>>> So the fix never got created and it did not revert from the update. >>>> >>>> Sorry for this mess. I will do a new patch to hopefully solve that problem for adding to Core Update 155, or you can revert sysvinit and I will make the update for the following Core Update. >>>> >>> Thinking about this while out walking the dog, I realised if the decision is to leave the updated package in Core Update 155 then I need to just create a patch for whatever fix is required to make it work properly on first boot. If the decision is to revert then I will need to create a patch for the full update again. I will work on creating a patch to just fix what is now in CU155 unless I hear differently from anyone. >>> >>> Regards, >>> >>> Adolf. >>> >> Back in early 2018 the sysvinit team decided to move the initctl pipe from /dev to /run. >> >> The commit message for this was "FreeBSD apparently does not like named pipes in /dev, so we move it to /run for better cross-platform compatibility." >> >> >> I installed CU155 from scratch and I had no problem at all. The pipe was in /run and nothing in /dev. >> >> It is when an upgrade is carried out and the system starts with the pipe in /dev, then the upgrade is not changing this. It is only changed after a forced reboot by doing a soft reset. >> >> It seems that we need some lines to remove the pipe from /dev and create it in /run at an appropriate stage of the upgrade. Is the lfs file the correct place to have these commands after the install commands or should they be in the file used to carry out the Core Update. The lfs file doesn't seem the correct place for this as it is only needed once for the upgrade from CU154 to CU155. After that the pipe will always stay in /run. >> >> >> I would appreciate advice on the best approach. If it should be in the upgrade script, where is that located? If it should be in the lfs do I just put the mknod command after the install command. >> >> >> Regards, >> >> Adolf. >> >>>> >>>> I also found the same problem with ssh not working after the update as mentioned in the forum post. >>>> >>>> Rebooting gave the following error message in the log. >>>> >>>> /usr/sbin/sshd: /lib/libcrypt.so.1: version `XCRYPT_2.0' not found (required by /usr/sbin/sshd) [FAIL] >>>> >>>> >>>> People on the forum had deleted the /lib/libcrypt.so.1 link, which was made to /lib/libcrypt-2.32.so and remade it to /usr/lib/libcrypt.so.1 and they have reported that ssh then works. I have not tried that fix yet. >>>> >>>> I checked the OpenSSH update patch I created and I didn't find anything related to libcrypt or a change of libcrypt location from /lib to /usr/lib >>>> >>>> >>>> Regards, >>>> >>>> Adolf >>>>

3 3

[PATCH] sudo: Update to 1.9.6p1
by Adolf Belka 17 Mar '21

17 Mar '21

- Update from 1.9.5p2 to 1.9.6p1 - Update not required for rootfile - Changelog Major changes between version 1.9.6p1 and 1.9.6: Fixed a regression introduced in sudo 1.9.6 that resulted in an error message instead of a usage message when sudo is run with no arguments. Major changes between version 1.9.6 and 1.9.5p2: Fixed a sudo_sendlog compilation problem with the AIX xlC compiler. Fixed a regression introduced in sudo 1.9.4 where the --disable-root-mailer configure option had no effect. Added a --disable-leaks configure option that avoids some memory leaks on exit that would otherwise occur. This is intended to be used with development tools that measure memory leaks. It is not safe to use in production at this time. Plugged some memory leaks identified by oss-fuzz and ASAN. Fixed the handling of sudoOptions for an LDAP sudoRole that contains multiple sudoCommands. Previously, some of the options would only be applied to the first sudoCommand. Fixed a potential out of bounds read in the parsing of NOTBEFORE and NOTAFTER sudoers command options (and their LDAP equivalents). The parser used for reading I/O log JSON files is now more resilient when processing invalid JSON. Fixed typos that prevented make uninstall from working. GitHub issue #87. Fixed a regression introduced in sudo 1.9.4 where the last line in a sudoers file might not have a terminating NUL character added if no newline was present. Integrated oss-fuzz and LLVM's libFuzzer with sudo. The new --enable-fuzzer configure option can be combined with the --enable-sanitizer option to build sudo with fuzzing support. Multiple fuzz targets are available for fuzzing different parts of sudo. Fuzzers are built and tested via make fuzz or as part of make check (even when sudo is not built with fuzzing support). Fuzzing support currently requires the LLVM clang compiler (not gcc). Fixed the --enable-static-sudoers configure option. GitHub issue #92. Fixed a potential out of bounds read sudo when is run by a user with more groups than the value of max_groups in sudo.conf. Added an admin_flag sudoers option to make the use of the ~/.sudo_as_admin_successful file configurable on systems where sudo is build with the --enable-admin-flag configure option. This mostly affects Ubuntu and its derivatives. GitHub issue #56. The max_groups setting in sudo.conf is now limited to 1024. This setting is obsolete and should no longer be needed. Fixed a bug in the tilde expansion of CHROOT=dir and CWD=dir sudoers command options. A path ~/foo was expanded to /home/userfoo instead of /home/user/foo. This also affects the runchroot and runcwd Defaults settings. Fixed a bug on systems without a native getdelim(3) function where very long lines could cause parsing of the sudoers file to end prematurely. Bug #960. Fixed a potential integer overflow when converting the timestamp_timeout and passwd_timeout sudoers settings to a timespec struct. The default for the group_source setting in sudo.conf is now dynamic on macOS. Recent versions of macOS do not reliably return all of a user's non-local groups via getgroups(2), even when _DARWIN_UNLIMITED_GETGROUPS is defined. Bug #946. Fixed a potential use-after-free in the PAM conversation function. Bug #967. Fixed potential redefinition of sys/stat.h macros in sudo_compat.h. Bug #968. Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org> --- lfs/sudo | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lfs/sudo b/lfs/sudo index bb2279e8f..6c09fac10 100644 --- a/lfs/sudo +++ b/lfs/sudo @@ -24,7 +24,7 @@ include Config -VER = 1.9.5p2 +VER = 1.9.6p1 THISAPP = sudo-$(VER) DL_FILE = $(THISAPP).tar.gz @@ -40,7 +40,7 @@ objects = $(DL_FILE) $(DL_FILE) = $(DL_FROM)/$(DL_FILE) -$(DL_FILE)_MD5 = e6bc4c18c06346e6b3431637a2b5f3d5 +$(DL_FILE)_MD5 = 334f8337d497f2f5df2db72448bd259d install : $(TARGET) -- 2.30.2

1 0

[PATCH] attr: Update to 2.5.1
by Adolf Belka 17 Mar '21

17 Mar '21

- Update from 2.4.48 to 2.5.1 - Update rootfile - Changelog Version 2.5.1 Fix libtool library versioning regression Andreas Gruenbacher Version 2.4.48 Update po files and German translation Andreas Gruenbacher getfattr: Add --one-file-system option Andreas Gruenbacher Move struct stat into struct walk_tree_args Andreas Gruenbacher Move list of open directories into struct walk_tree_args Andreas Gruenbacher Move walk_tree_rec arguments into a separate struct Andreas Gruenbacher xattr.conf: Indicate afs metadata xattrs should be skipped when copying David Howells Fix typos in manual pages Samanta Navarro Update my email address Andreas Gruenbacher man: add examples to setfattr.1 Achilles Gaikwad install-data: Don't remove unrelated empty directories Andreas Gruenbacher attr: Replace bzero with memset Rosen Penev getfattr: don't count terminating NULL in well_enough_printable Jeff Layton attr_list, attr_listf: Guard against unterminated buffer Andreas Gruenbacher attr_multi, attr_multif: Don't set errno to -EINVAL Andreas Gruenbacher Switch back to syscall() Andreas Gruenbacher attr_list.3: Fix the attributes.h include path Andreas Gruenbacher getfattr.1: by default only user namespace attributes are dumped Simon Ruderich Enable large-file support on systems that do not enable it by default Dmitry V. Levin man: standardize AUTHORS section Mike Frysinger man: fix bold style in SEE ALSO section Mike Frysinger test: escape left brace in a regex in test/run Troy Dawson Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org> --- config/rootfiles/common/attr | 2 +- lfs/attr | 8 ++++---- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/config/rootfiles/common/attr b/config/rootfiles/common/attr index ba3ed7db7..536cfb9fc 100644 --- a/config/rootfiles/common/attr +++ b/config/rootfiles/common/attr @@ -11,7 +11,7 @@ usr/bin/setfattr #usr/lib/libattr.la #usr/lib/libattr.so usr/lib/libattr.so.1 -usr/lib/libattr.so.1.1.2448 +usr/lib/libattr.so.1.1.2501 #usr/lib/pkgconfig/libattr.pc #usr/share/doc/attr #usr/share/doc/attr/CHANGES diff --git a/lfs/attr b/lfs/attr index e1edd6076..6c8db290c 100644 --- a/lfs/attr +++ b/lfs/attr @@ -24,10 +24,10 @@ include Config -VER = 2.4.48 +VER = 2.5.1 THISAPP = attr-$(VER) -DL_FILE = $(THISAPP).tar.gz +DL_FILE = $(THISAPP).tar.xz DL_FROM = $(URL_IPFIRE) DIR_APP = $(DIR_SRC)/$(THISAPP) TARGET = $(DIR_INFO)/$(THISAPP) @@ -40,7 +40,7 @@ objects = $(DL_FILE) $(DL_FILE) = $(DL_FROM)/$(DL_FILE) -$(DL_FILE)_MD5 = bc1e5cb5c96d99b24886f1f527d3bb3d +$(DL_FILE)_MD5 = e459262266bbd82b3dd348fc8cc68a6d install : $(TARGET) @@ -69,7 +69,7 @@ $(subst %,%_MD5,$(objects)) : $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects)) @$(PREBUILD) - @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar zxf $(DIR_DL)/$(DL_FILE) + @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar axf $(DIR_DL)/$(DL_FILE) $(UPDATE_AUTOMAKE) cd $(DIR_APP) && ./configure cd $(DIR_APP) && make -- 2.30.2

1 0

[PATCH] acl: Update to 2.3.1
by Adolf Belka 17 Mar '21

17 Mar '21

- Update from 2.2.53 to 2.3.1 - Updated rootfile - Changelog Version 2.3.1 Fix libtool library versioning regression Andreas Gruenbacher Version 2.3.0 Update po files and German translation Andreas Gruenbacher getfacl: fix indent in --help output Valentin Vidic getfacl: Add --one-file-system optionnext Pavel Polacek Move struct stat into struct walk_tree_args Andreas Gruenbacher Move list of open directories into struct walk_tree_args Andreas Gruenbacher Move walk_tree_rec arguments into a separate struct Andreas Gruenbacher acl_from_mode, acl_copy_int: Fix segfault on allocation failure Tavian Barnes __acl_create_entry_obj: do not break strict aliasing rules Kamil Dudka Fix typo in getfacl(1) man page Anthony Sottile Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org> --- config/rootfiles/common/acl | 6 +----- lfs/acl | 6 +++--- 2 files changed, 4 insertions(+), 8 deletions(-) diff --git a/config/rootfiles/common/acl b/config/rootfiles/common/acl index 19ce21ca0..a3476d9a5 100644 --- a/config/rootfiles/common/acl +++ b/config/rootfiles/common/acl @@ -7,7 +7,7 @@ usr/bin/setfacl #usr/lib/libacl.la usr/lib/libacl.so usr/lib/libacl.so.1 -usr/lib/libacl.so.1.1.2253 +usr/lib/libacl.so.1.1.2301 #usr/lib/pkgconfig/libacl.pc #usr/share/doc/acl #usr/share/doc/acl/CHANGES @@ -17,11 +17,7 @@ usr/lib/libacl.so.1.1.2253 #usr/share/doc/acl/extensions.txt #usr/share/doc/acl/libacl.txt #usr/share/locale/de/LC_MESSAGES/acl.mo -#usr/share/locale/en@boldquot -#usr/share/locale/en@boldquot/LC_MESSAGES #usr/share/locale/en(a)boldquot/LC_MESSAGES/acl.mo -#usr/share/locale/en@quot -#usr/share/locale/en@quot/LC_MESSAGES #usr/share/locale/en(a)quot/LC_MESSAGES/acl.mo #usr/share/locale/es/LC_MESSAGES/acl.mo #usr/share/locale/fr/LC_MESSAGES/acl.mo diff --git a/lfs/acl b/lfs/acl index 5cf262ef9..cecdb8334 100644 --- a/lfs/acl +++ b/lfs/acl @@ -24,10 +24,10 @@ include Config -VER = 2.2.53 +VER = 2.3.1 THISAPP = acl-$(VER) -DL_FILE = $(THISAPP).tar.gz +DL_FILE = $(THISAPP).tar.xz DL_FROM = $(URL_IPFIRE) DIR_APP = $(DIR_SRC)/$(THISAPP) TARGET = $(DIR_INFO)/$(THISAPP) @@ -40,7 +40,7 @@ objects = $(DL_FILE) $(DL_FILE) = $(DL_FROM)/$(DL_FILE) -$(DL_FILE)_MD5 = 007aabf1dbb550bcddde52a244cd1070 +$(DL_FILE)_MD5 = 95ce715fe09acca7c12d3306d0f076b2 install : $(TARGET) -- 2.30.2

1 0

Feedback on Core Update 155 Testing
by Adolf Belka 17 Mar '21

17 Mar '21

Dear all, There is feedback on the forum about IPFire not rebooting after update and needing a soft reset. After that it boots again. I also found the same effect on my VM testbed system for testing. https://community.ipfire.org/t/feedback-core-update-155-testing/4896 That symptom triggered my memory (a bit late) and I found the discussion about my sysvinit patch. https://lists.ipfire.org/pipermail/development/2021-February/009403.html So the fix never got created and it did not revert from the update. Sorry for this mess. I will do a new patch to hopefully solve that problem for adding to Core Update 155, or you can revert sysvinit and I will make the update for the following Core Update. I also found the same problem with ssh not working after the update as mentioned in the forum post. Rebooting gave the following error message in the log. /usr/sbin/sshd: /lib/libcrypt.so.1: version `XCRYPT_2.0' not found (required by /usr/sbin/sshd) [FAIL] People on the forum had deleted the /lib/libcrypt.so.1 link, which was made to /lib/libcrypt-2.32.so and remade it to /usr/lib/libcrypt.so.1 and they have reported that ssh then works. I have not tried that fix yet. I checked the OpenSSH update patch I created and I didn't find anything related to libcrypt or a change of libcrypt location from /lib to /usr/lib Regards, Adolf -- Sent from my laptop

2 4

Planning Core Update 155
by Michael Tremer 15 Mar '21

15 Mar '21

Hello everyone, I wanted to open a quick thread to organise what is going into the next Core Update which I planned on closing soon so that people have more time to test the ALG changes that have been announced yesterday: https://blog.ipfire.org/post/security-announcement-mitigating-nat-slipstrea… It was being quiet and so I wanted to wait until armv5tel finally builds again and then branch the update. Now there is a massive wave of packages from Adolf which should probably be included in this release. Just to keep the backlog as small as possible. Does anybody else have any pending changes that should go into c155? Best, -Michael

2 3

[PATCH] dhcpcd: Update to 9.4.0
by Matthias Fischer 15 Mar '21

15 Mar '21

For details see: https://roy.marples.name/archives/dhcpcd-discuss/0003420.html Former patch for Bug #12552 is now included. Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org> --- lfs/dhcpcd | 7 ++-- ...r_SECCOMP_as_it_just_uses_socketcall.patch | 36 ------------------- 2 files changed, 2 insertions(+), 41 deletions(-) delete mode 100644 src/patches/dhcpcd/01_Fix_Linux_i386_for_SECCOMP_as_it_just_uses_socketcall.patch diff --git a/lfs/dhcpcd b/lfs/dhcpcd index 4e34e19d5..352308692 100644 --- a/lfs/dhcpcd +++ b/lfs/dhcpcd @@ -24,7 +24,7 @@ include Config -VER = 9.3.4 +VER = 9.4.0 THISAPP = dhcpcd-$(VER) DL_FILE = $(THISAPP).tar.xz @@ -40,7 +40,7 @@ objects = $(DL_FILE) $(DL_FILE) = $(DL_FROM)/$(DL_FILE) -$(DL_FILE)_MD5 = badb02dfc69fe9bbeec35a02efcdb4db +$(DL_FILE)_MD5 = c36715fc629bc40aa94aae06fa1724c2 install : $(TARGET) @@ -70,9 +70,6 @@ $(subst %,%_MD5,$(objects)) : $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects)) @$(PREBUILD) @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar axf $(DIR_DL)/$(DL_FILE) - - cd $(DIR_APP) && patch -Np1 -i $(DIR_SRC)/src/patches/dhcpcd/01_Fix_Linux_i386_for_SECCOMP_as_it_just_uses_socketcall.patch - cd $(DIR_APP) && ./configure --prefix="" --sysconfdir=/var/ipfire/dhcpc \ --dbdir=/var/ipfire/dhcpc \ --libexecdir=/var/ipfire/dhcpc \ diff --git a/src/patches/dhcpcd/01_Fix_Linux_i386_for_SECCOMP_as_it_just_uses_socketcall.patch b/src/patches/dhcpcd/01_Fix_Linux_i386_for_SECCOMP_as_it_just_uses_socketcall.patch deleted file mode 100644 index 9efcde219..000000000 --- a/src/patches/dhcpcd/01_Fix_Linux_i386_for_SECCOMP_as_it_just_uses_socketcall.patch +++ /dev/null @@ -1,36 +0,0 @@ -diff --git a/src/privsep-linux.c b/src/privsep-linux.c -index 050a30cf..d31d720d 100644 ---- a/src/privsep-linux.c -+++ b/src/privsep-linux.c -@@ -32,6 +32,7 @@ - - #include <linux/audit.h> - #include <linux/filter.h> -+#include <linux/net.h> - #include <linux/seccomp.h> - #include <linux/sockios.h> - -@@ -304,6 +305,23 @@ static struct sock_filter ps_seccomp_filter[] = { - #ifdef __NR_sendto - SECCOMP_ALLOW(__NR_sendto), - #endif -+#ifdef __NR_socketcall -+ /* i386 needs this and demonstrates why SECCOMP -+ * is poor compared to OpenBSD pledge(2) and FreeBSD capsicum(4) -+ * as this is soooo tied to the kernel API which changes per arch -+ * and likely libc as well. */ -+ SECCOMP_ALLOW_ARG(__NR_socketcall, 0, SYS_ACCEPT), -+ SECCOMP_ALLOW_ARG(__NR_socketcall, 0, SYS_ACCEPT4), -+ SECCOMP_ALLOW_ARG(__NR_socketcall, 0, SYS_LISTEN), -+ SECCOMP_ALLOW_ARG(__NR_socketcall, 0, SYS_GETSOCKOPT), /* overflow */ -+ SECCOMP_ALLOW_ARG(__NR_socketcall, 0, SYS_RECV), -+ SECCOMP_ALLOW_ARG(__NR_socketcall, 0, SYS_RECVFROM), -+ SECCOMP_ALLOW_ARG(__NR_socketcall, 0, SYS_RECVMSG), -+ SECCOMP_ALLOW_ARG(__NR_socketcall, 0, SYS_SEND), -+ SECCOMP_ALLOW_ARG(__NR_socketcall, 0, SYS_SENDMSG), -+ SECCOMP_ALLOW_ARG(__NR_socketcall, 0, SYS_SENDTO), -+ SECCOMP_ALLOW_ARG(__NR_socketcall, 0, SYS_SHUTDOWN), -+#endif - #ifdef __NR_shutdown - SECCOMP_ALLOW(__NR_shutdown), - #endif -- 2.18.0

3 2

Re: Porting IPFire 2 to RISC-V
by Michael Tremer 10 Mar '21

10 Mar '21

Hello Furkan, Thank you very much for your thoughts. I think you might have misunderstood me on a few things. > On 10 Mar 2021, at 15:18, Furkan Salman <tech(a)fkardame.com> wrote: > > Hello, > > RISC-V is too new to look into it, even I am waiting for some test board from either BeagleBoard or SiFive. There are some other OEM doing it but it is not based on a powerful SOC which can be used to compile the packages. Yes, this is what I was trying to say. RISC-V isn’t ready, yet and I wasn’t expecting it to be. I wanted to do some research into this new architecture and nothing more, yet. > Pine64 have announced something but it is a RPI Zero type board under $15 This can be used to test things out but not for regular build process. What I should have made clear is that when I say RISC-V, I am talking about the 64 bit version that could potentially replace x86. I do not have any interest in small boards that even use the 32 bit instruction set because those are not powerful enough for what we are doing with IPFire. > Currently due to silicon shortage no manufacturer is able to ship hardware as per their expectation. > With this new architecture I do not expect anything to be usable at this stage, from my point of view it will take around 2 years for good support to be added to the linux kernel. I do not understand your desire to get IPFire to work on RISC-V when we do not even have ARM stable support for well known ARM based Network hardware. Very good point. I have written in various places that I do not expect ARM to stabilise any time soon - if at all. The boards that we currently support are basically no longer available to purchase - or there are some remaining units on the shelves after a successor has already come out. No vendor has tried to invest any of their time to help out software developers. Teams of volunteers have reverse engineered and written drivers, cleaned up loads of code that was dropped by a vendor and after they were done, the next product came out which was entirely incompatible with its predecessor. This is not an ecosystem that is sustainable for the software industry and I believe it is time that we admit that. There is no major distribution that supports various modern ARM boards out of the box. Not Debian, not Fedora, not SuSE, not Gentoo. Instead there are “special” distributions doing this work with varying success. RedHat has been trying to make ARM popular on servers and that does not seem to have been very popular either. They relied on UEFI to have a common denominator and they wanted to run the same image on all hardware. It worked - that is not what I want to dispute here, but that kind of hardware is not freely available to purchase, or if it is, simply too expensive that not many people will buy it. I do not think this will be fixed. Vendors haven’t learned and they are probably making their money by selling people loads of “name your fruit” Pis that are being collected in people’s draws - but probably not being used. > Adding RISC-V will be another burden on you. Another reason that can add burden to Ipfire fire team is that Risc-V will also use DTS only and no UEFI support yet which means maintaining individual device support with its specific dts and bootloader is not easy task which can be seen in the ARM support already. DTS isn’t a problem for us as long as the boot loader is initialising the hardware and sending the kernel the device tree. > I would request you to acquire some good ARM boards and create a ready to build images for those, We can try to get the manufacturers ship IPFire as Default OS instead on OpenWRT. Once we start getting more ARM user then we can promote RISC-V when RISC-V Hardware becomes openly available. Serious questions: What is a “good” ARM board? I do not know any that have good CPU performance, about four Gigabit Ethernet adapters and space for an SSD and a WiFi module that cost less than US$600. You get that for a lot less money if you use x86. USB networking is not an option and a terrible problem coming from ARM being optimised for mobile use. There is no need for a PCI bus or Ethernet in the SoC. Instead it had to be added afterwards. RISC-V looks like it is designed to be more of an allrounder processor. The boards that came out so far have proper networking which puts us in a totally different position than with ARM. > I am still waiting to try IPFire with a Linux Kernel which have good support for the current available ARM Boards. I have been busy with other support work so I have not got time to look into the newer IPFire where I can use latest kernel and enable Most of the ARM SOC Support. > > I can try to get a RISC-V Board for you from Pine64 but again this is not yet announced and it might take 2-3 months for production after being announced, It is XuanTie C906 processor sbc which should be equivalent to ARM A55 core, no idea about how many cores will be used. I googled the SoC and it seems to come with a single core clocked at 1 GHz. This is indeed more equivalent to the Raspberry Pi Zero which is not powerful enough to run IPFire. > Currently IPFire project is in need to move to latest Kernel so most of the ARM boards can get support while RISC-V board support is also getting merged. To support any new Architecture we will always have to use latest kernel to get the device support. I have tried backporting things to older kernel but that is just a waste of time when we can just use the latest kernel and fix stuff upstream. There are various reasons why we cannot always be on the latest kernel. It takes us a long time to get IPFire stable on a certain release and we cannot do this too often. Just for reference, Arne’s development tree is here: https://git.ipfire.org/?p=people/arne_f/ipfire-2.x.git;a=shortlog;h=refs/he… I am sure he would be happy to accept patches - we have talked about this many times before. > In short we need to focus more on ARM for now until RISC-V hardware is available for testing. ARM Image build tool need to be enhanced to build device specific images which will have a pre-flashed bootloader as done by most of the distro like Armbian, Manjaro ARM, LibreElec, OpnSense etc. Expecting a network engineer to flash a generic arm image to sd and then flash a bootloader is not practical as understanding how ARM/RISC-V works is not known to everyone who have never tried it. Having a ready to flash image can make things easy for IPFire Users. > IPFire supports ARM official still I do not see many community contributors on the mailing list or forum, while Freebsd and Opnsense doesn't even support ARM officially but still I see many contributors on their forum. i hope you understand what I am trying to compare here. We need more ARM user and contributors and to get this we will need ready to flash images for well known network boards. I have already informed in forum that the boards that are currently support have reached EOL and are no longer sold by the manufacturer plus those are not powerful enough. Yes, see above. This is the game we are playing here. It is actually ARM that is slowing down migrating to a new kernel release. Things that worked before no longer work. The time that is lacking to add support for more hardware is being spent to keep old hardware working. > I can also ask FriendlyARM to send you R4S sample but that is out of stock and they have no idea when it will be ready as there is no supply of DDR4 ram chips. If we can get Rk3399 & RK3328 board support then this will open support to many other boards based on these SOC, while we work on RK33xx support, Rockchip have already released RK35xx and I have already received RK3566 board for testing but there is no mainline linux support and I expect it to take around a year to get basic support for it which will be the same for RISC-V. And the vendor is expecting us to simply patch our software to support this hardware? If it isn’t in mainline, we probably can’t support it. How large should the team be? And looking at our user base, I am not sure if there are boards that have more than a hand full of users. To repeat myself once again: I do not think that this is a very sustainable situation and I was curious to find out whether anything is different on RISC-V. The grass is always greener on the other side. Time will tell if I am right or wrong. Best, -Michael > Let us work on using Latest Linux Kernel to get newer ARM SOC to work then we can look into RISC-V as from what I understand compiling pkgs for RISC-V is not a be task. > > This is what I think from my experience of supporting ARM Devices support at Manjaro ARM project. > > Regards, > Furkan K. > > > > > ---- On Mon, 08 Mar 2021 20:27:51 +0300 Michael Tremer <michael.tremer(a)ipfire.org> wrote ---- > > Hello, > > Apologies that this email comes a bit late and my changes have caused some confusion on the list, but better late than never. > > I have spent some time to port IPFire 2 to RISC-V. This is nothing that had a very high priority, but I wanted to get my hands on it to see whether it was “just another architecture” that could bring us 1% of users, or if it was different from ARM which we already support as an alternative architecture to x86. > > To keep it short, RISC-V seems to be very different. In a good way. But it is too soon. > > The bootstrap for ARM took many months whereas this port compiled almost on the first go. There were some issues with autotools, but no bigger linker issues in the toolchain, assembly errors or simply where a build process broken because it didn’t recognise the architecture. The only exception was that PCRE/PCRE2 do not have support for RISC-V for their JIT, yet. > > Therefore I decided to merge the branch with all required changes into the main repository because there are no changes that will break anything else. This was a very nice experience. As a package maintainer, you probably just switch on RISC-V and you are done. > > There are, however, a couple of downsides. The biggest one is that I didn’t have hardware and that there isn’t much available at this point in time. The development boards are too expensive and I didn’t even consider to buy one because even if I could compile IPFire for RISC-V in reasonable time, literally nobody will be able to use it. > > With ARM, we were quite early and we can only conclude that that wasn’t a good thing. We ran into loads of problems with the architecture and we still have *very* limited choice of hardware available. At least RISC-V does not seem to cause these issues on the software development side, which might make support for it a lot less painful for us. Yay. > > I have used QEMU to emulate the whole architecture and it can be built on any machine that has qemu-system-riscv64 installed. Please do not forget to download the toolchain first. Although QEMU is fast, compiling it took about three days on a 12-core Xeon processor that was a little bit dated actually. > > One of the biggest pain points is Rust which isn’t available at all for RISC-V and therefore I could not build suricata. Due to the lack of real-world application for this and our limited usage of Rust this won’t be a problem for now, but probably further down the line. > > So, what we are going to do with it? > > I will probably compile it every once in a while just to check if it is still compiling. There is no point in uploading it to a server yet because nobody will be able to use it. > > I unfortunately have no connection to the (RISC-V) hardware industry. If someone does have such connection, please let me know. It would be great to have some development hardware to use and make IPFire boot on it. We would also require some strong build power to not delay development because of adding another architecture. > > Those are my thoughts on this :) > > -Michael > >

1 0

[PATCH] elfutils: Update to 0.183
by Adolf Belka (ipfire) 10 Mar '21

10 Mar '21

- Update elfutils from 0.182 to 0.183 - Updated rootfiles - Changelog 2021-02-05 Mark Wielaard <mark(a)klomp.org> * configure.ac (AC_INIT): Set version to 0.183. (AC_COPYRIGHT): Update Copyright year. * NEWS: Add 0.183 section. 2021-02-01 Érico Nogueira <ericonr(a)disroot.org> * configure.ac: Check for GNU strerror_r. 2021-01-12 Dmitry V. Levin <ldv(a)altlinux.org> * configure.ac [--enable-gcov]: Check for gcov, lcov, and genhtml. * Makefile.am [GCOV] (coverage, coverage-clean): New targets. * .gitignore: Update. 2020-12-20 Dmitry V. Levin <ldv(a)altlinux.org> * .gitignore: Move subdirectory patterns to separate .gitignore files. * .gitignore: Update. 2020-12-15 Dmitry V. Levin <ldv(a)altlinux.org> * configure.ac (USE_NLS, AM_PO_SUBDIRS): Remove. (AM_GNU_GETTEXT, AM_GNU_GETTEXT_VERSION, AM_GNU_GETTEXT_REQUIRE_VERSION): Use these macros to setup the gettext infrastructure. * .gitignore: Update. * Makefile.am (SUBDIRS): Remove m4. * configure.ac (AC_CONFIG_FILES): Remove m4/Makefile. * configure.ac (AC_CONFIG_MACRO_DIR): Remove. 2020-12-12 Dmitry V. Levin <ldv(a)altlinux.org> * configure.ac: Fix spelling typos in comments. * NEWS: Fix spelling typos. * NOTES: Likewise. * TODO: Likewise. 2020-12-11 Dmitry V. Levin <ldv(a)altlinux.org> * configure.ac (AM_CONDITIONAL): Remove HAVE_LIBASM and STANDALONE. * configure.ac: Rewrite argp check. * configure.ac (AC_MSG_FAILURE): Fix typo. 2020-11-30 Dmitry V. Levin <ldv(a)altlinux.org> * configure.ac (LIBDEBUGINFOD_SONAME): New AC_SUBST variable. (AC_CONFIG_FILES): Add debuginfod/debuginfod.h. 2020-11-01 Érico N. Rolim <erico.erc(a)gmail.com> * configure.ac: Check for fts and obstack from outside libc. Signed-off-by: Adolf Belka (ipfire) <adolf.belka(a)ipfire.org> --- config/rootfiles/packages/elfutils | 12 ++++++------ lfs/elfutils | 6 +++--- 2 files changed, 9 insertions(+), 9 deletions(-) diff --git a/config/rootfiles/packages/elfutils b/config/rootfiles/packages/elfutils index f7826ec11..adf4808ab 100644 --- a/config/rootfiles/packages/elfutils +++ b/config/rootfiles/packages/elfutils @@ -27,17 +27,17 @@ usr/bin/eu-unstrip #usr/include/gelf.h #usr/include/libelf.h #usr/include/nlist.h -usr/lib/libasm-0.182.so +usr/lib/libasm-0.183.so #usr/lib/libasm.a -usr/lib/libasm.so +#usr/lib/libasm.so usr/lib/libasm.so.1 -usr/lib/libdw-0.182.so +usr/lib/libdw-0.183.so #usr/lib/libdw.a -usr/lib/libdw.so +#usr/lib/libdw.so usr/lib/libdw.so.1 -usr/lib/libelf-0.182.so +usr/lib/libelf-0.183.so #usr/lib/libelf.a -usr/lib/libelf.so +#usr/lib/libelf.so usr/lib/libelf.so.1 #usr/lib/pkgconfig/libdw.pc #usr/lib/pkgconfig/libelf.pc diff --git a/lfs/elfutils b/lfs/elfutils index 19311d7aa..c2d9a3331 100644 --- a/lfs/elfutils +++ b/lfs/elfutils @@ -24,7 +24,7 @@ include Config -VER = 0.182 +VER = 0.183 THISAPP = elfutils-$(VER) DL_FILE = $(THISAPP).tar.bz2 @@ -32,7 +32,7 @@ DL_FROM = $(URL_IPFIRE) DIR_APP = $(DIR_SRC)/$(THISAPP) TARGET = $(DIR_INFO)/$(THISAPP) PROG = elfutils -PAK_VER = 3 +PAK_VER = 4 DEPS = @@ -44,7 +44,7 @@ objects = $(DL_FILE) $(DL_FILE) = $(DL_FROM)/$(DL_FILE) -$(DL_FILE)_MD5 = ebd95e1858280095fd60d0f765d50fef +$(DL_FILE)_MD5 = 6f58aa1b9af1a5681b1cbf63e0da2d67 install : $(TARGET) -- 2.30.2

3 2

← Newer
1
...
5
6
7
8
9
10
11
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

Development March 2021