LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 01-25-2022, 03:21 AM   #316
semiprime
Member
 
Registered: Apr 2019
Location: UK
Distribution: Slackware
Posts: 51

Rep: Reputation: 59

Quote:
a/kernel-generic-5.15.16-x86_64-2.txz: Upgraded.
a/kernel-huge-5.15.16-x86_64-2.txz: Upgraded.
...
a/kernel-modules-5.15.16-x86_64-2.txz: Upgraded.
...
d/kernel-headers-5.15.16-x86-2.txz: Upgraded.
k/kernel-source-5.15.16-noarch-2.txz: Upgraded.
That's weird.

We were already on kernel 5.15.16. Why aren't they "Rebuilt"?

Last edited by semiprime; 01-25-2022 at 03:32 AM. Reason: +modules
 
1 members found this post helpful.
Old 01-25-2022, 03:31 AM   #317
avian
Member
 
Registered: Aug 2014
Posts: 184

Rep: Reputation: Disabled
Quote:
Originally Posted by semiprime View Post
That's weird.

We were already on kernel 5.15.16. Why aren't they "Rebuilt"?
Interesting pick up.

Last edited by avian; 01-25-2022 at 03:33 AM. Reason: Misunderstood post.
 
Old 01-25-2022, 04:03 AM   #318
marav
LQ Sage
 
Registered: Sep 2018
Location: Gironde
Distribution: Slackware
Posts: 5,448

Original Poster
Rep: Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208
I just hope Pat doesn't mess up my script with the next changelog.
 
Old 01-25-2022, 05:36 AM   #319
baumei
Member
 
Registered: Feb 2019
Location: USA; North Carolina
Distribution: Slackware 15.0 (replacing 14.2)
Posts: 365

Rep: Reputation: 124Reputation: 124
The package name of the previous kernel is "5.15.16-x86_64-1.txz", and the package name of the new kernel is "5.15.16-x86_64-2.txz". Apparently, there is some sort of difference. I wonder if the upstream kernel source discovered a severe small error, and sent out an early fix which did not involve a change from "5.15.16" to 5.15.17"?

Quote:
Originally Posted by semiprime View Post
That's weird.

We were already on kernel 5.15.16. Why aren't they "Rebuilt"?
 
Old 01-25-2022, 05:43 AM   #320
marav
LQ Sage
 
Registered: Sep 2018
Location: Gironde
Distribution: Slackware
Posts: 5,448

Original Poster
Rep: Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208
Quote:
Originally Posted by baumei View Post
The package name of the previous kernel is "5.15.16-x86_64-1.txz", and the package name of the new kernel is "5.15.16-x86_64-2.txz". Apparently, there is some sort of difference. I wonder if the upstream kernel source discovered a severe small error, and sent out an early fix which did not involve a change from "5.15.16" to 5.15.17"?
nope
They never do that. Each time they merge a fix in the kernel, it will be available only in the next release
This "new" Slackware kernel includes :
Code:
a/kernel-huge-5.15.16-x86_64-2.txz:  Upgraded.
  -9P_FSCACHE n
   9P_FS m -> y
I can't explain the "Upgraded" label ... but I'm not against staying like this
P.S: maybe Pat wants to see if we are still on guard.

Last edited by marav; 01-25-2022 at 05:49 AM.
 
1 members found this post helpful.
Old 01-25-2022, 11:37 AM   #321
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 2,553

Rep: Reputation: 8567Reputation: 8567Reputation: 8567Reputation: 8567Reputation: 8567Reputation: 8567Reputation: 8567Reputation: 8567Reputation: 8567Reputation: 8567Reputation: 8567
Quote:
Originally Posted by semiprime View Post
That's weird.

We were already on kernel 5.15.16. Why aren't they "Rebuilt"?
Probably because my script that merges kernel packages is not the same one that I use for other packages and hasn't had a lot of testing with $BUILD != 1. Sorry about that, yes those packages should have said "Rebuilt."
 
5 members found this post helpful.
Old 01-25-2022, 11:39 AM   #322
marav
LQ Sage
 
Registered: Sep 2018
Location: Gironde
Distribution: Slackware
Posts: 5,448

Original Poster
Rep: Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208
Quote:
Originally Posted by volkerdi View Post
Probably because my script that merges kernel packages is not the same one that I use for other packages and hasn't had a lot of testing with $BUILD != 1. Sorry about that, yes those packages should have said "Rebuilt."
Grrr

Will the next changelog diff mess up my script?
So, I can correct it before

Last edited by marav; 01-25-2022 at 11:40 AM.
 
Old 01-25-2022, 01:24 PM   #323
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 2,553

Rep: Reputation: 8567Reputation: 8567Reputation: 8567Reputation: 8567Reputation: 8567Reputation: 8567Reputation: 8567Reputation: 8567Reputation: 8567Reputation: 8567Reputation: 8567
Quote:
Originally Posted by marav View Post
Grrr

Will the next changelog diff mess up my script?
So, I can correct it before
I guess I'd be inclined to correct the error in the latest ChangeLog, but really it doesn't matter all that much. Would you prefer that I left it alone?
 
Old 01-25-2022, 01:38 PM   #324
marav
LQ Sage
 
Registered: Sep 2018
Location: Gironde
Distribution: Slackware
Posts: 5,448

Original Poster
Rep: Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208
Quote:
Originally Posted by volkerdi View Post
I guess I'd be inclined to correct the error in the latest ChangeLog, but really it doesn't matter all that much. Would you prefer that I left it alone?
It's up to you. But, If it doesn't matter, yes
Otherwise, let me know, so that I can modify it now

Last edited by marav; 01-25-2022 at 01:44 PM.
 
Old 01-25-2022, 01:49 PM   #325
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 2,553

Rep: Reputation: 8567Reputation: 8567Reputation: 8567Reputation: 8567Reputation: 8567Reputation: 8567Reputation: 8567Reputation: 8567Reputation: 8567Reputation: 8567Reputation: 8567
Quote:
Originally Posted by marav View Post
It's up to you. But, If it doesn't matter, yes
Otherwise, let me know, so that I can modify it now
It's no big deal. I'll leave it the way it is.
 
1 members found this post helpful.
Old 01-25-2022, 02:18 PM   #326
marav
LQ Sage
 
Registered: Sep 2018
Location: Gironde
Distribution: Slackware
Posts: 5,448

Original Poster
Rep: Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208
3 updates (x86_64) : 2 upgraded, 1 rebuilt
Code:
Tue Jan 25 20:10:35 UTC 2022
d/icecream-1.3.1-x86_64-4.txz:  Rebuilt.
  rc.icecream.conf: generate an error message and avoid a hang when
  "hostname -d" doesn't work, usually because the hostname in /etc/HOSTNAME
  can't be resolved. Thanks to franzen.
kde/latte-dock-0.10.8-x86_64-1.txz:  Upgraded.
xap/geeqie-1.7.2-x86_64-1.txz:  Upgraded.
Provided by http://marav8.free.fr/report/slack_LQ.txt
 
Old 01-25-2022, 02:56 PM   #327
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,078

Rep: Reputation: Disabled
Quote:
Originally Posted by marav View Post
Code:
xap/geeqie-1.7.2-x86_64-1.txz: Upgraded.
Who told me "You really think my post has any influence on this?"
 
Old 01-25-2022, 03:30 PM   #328
marav
LQ Sage
 
Registered: Sep 2018
Location: Gironde
Distribution: Slackware
Posts: 5,448

Original Poster
Rep: Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208Reputation: 4208
Quote:
Originally Posted by Didier Spaier View Post
Who told me "You really think my post has any influence on this?"
Indeed
And I will complain, I don’t know why latte-dock was upgraded, I didn’t ask for it

PS : off topic but, why don't you ask Patrick directly how many packages he plans to update again and when 15.0 will be released?

Last edited by marav; 01-25-2022 at 03:39 PM.
 
Old 01-25-2022, 03:59 PM   #329
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,078

Rep: Reputation: Disabled
Quote:
Originally Posted by marav View Post
PS : off topic but, why don't you ask Patrick directly how many packages he plans to update again and when 15.0 will be released?
I do not need to know how many packages he plans to update (and there can be unplanned updates until the last minute) and I know since a very long time that he would not answer to "when" (actually he did a few minutes ago but as the saying goes "exceptio probat regulam").

Last edited by Didier Spaier; 01-25-2022 at 04:02 PM.
 
Old 01-25-2022, 04:02 PM   #330
kjhambrick
Senior Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 15.0 + Multilib
Posts: 2,159

Rep: Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512
All --

Somewhat Scary glibc update with Tue Jan 25 06:16:36 UTC 2022 because I run Slackware Current + Multilib.

Everything is fine, thanks to Alien Bob's timely rebuilds of the Slackware Current Multilib glibc packages.
Code:
# ver glibc
-rw-r--r-- 1 root root  15496 Jan 25 15:39 /var/log/packages/aaa_glibc-solibs-2.33_multilib-x86_64-5alien
-rw-r--r-- 1 root root  33635 Jan 25 15:39 /var/log/packages/glibc-2.33_multilib-x86_64-5alien
-rw-r--r-- 1 root root 519335 Jan 25 15:39 /var/log/packages/glibc-i18n-2.33_multilib-x86_64-5alien
-rw-r--r-- 1 root root   1238 Jan 25 15:39 /var/log/packages/glibc-profile-2.33_multilib-x86_64-5alien
-rw-r--r-- 1 root root  71721 Nov  7 04:35 /var/log/packages/glibc-zoneinfo-2021e-noarch-1 # noarch package
Thanks to Eric and the Slackware Team !

-- kjh
 
2 members found this post helpful.
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Latest Firefox (88.0.1) has trouble with -current changelog... andrew.46 Slackware 5 05-10-2021 04:59 AM
Wrong ChangeLog for Slackware Current? rsamurti Slackware 5 06-28-2020 01:46 AM
Latest Xorg changelog effect brodo Slackware 12 09-22-2008 01:17 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 08:52 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration