LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
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
 
LinkBack Search this Thread
Old 07-04-2012, 11:45 AM   #1
Luiz Ramos
LQ Newbie
 
Registered: Jun 2010
Location: São Paulo - Brazil
Distribution: Slackware, Debian
Posts: 17

Rep: Reputation: 1
About GSB-3.2 repositories


Hello,

A question about GnomeSlackBuild repositories. For instance, about this mirror:

http://mirror.switch.ch/ftp/mirror/g...are-13.37/gsb/

It seems the file CHECKSUMS.md5 is corrupted. slapt-get --update shows that, anyway, although the signature is good (however expired). But it is not real corrupted, in fact, as I'll try to demonstrate next.

What seems to be happening is that the file format isn't properly recognized by md5sum -c, for instance (and probably by slapt-get as well).

The checksums file has some lines of header and a list of lines such as "<hash> <filename>". Both items are separated by two spaces. If I edit that file and cut one space off, "md5sum -c" begins to work as desired.

A similar effect can be seen if the header is stripped off the file.

Anyway, the final result is that slapt-get gets unuseful in this case.

My two questions are: (1) is there anybody there who saw this as myself (that is, is there any mistake in my findings, or is there any other GSB user out there)?, and (2) how to manage this in order to restore service, in case of (1) being true.

Thanks,

Luiz Ramos
São Paulo - Brazil
 
Old 07-05-2012, 11:55 PM   #2
tallship
Member
 
Registered: Jul 2003
Location: On the Beaches of Super Sunny Southern San Clemente, California USA
Distribution: Slackware - duh!
Posts: 520
Blog Entries: 3

Rep: Reputation: 112Reputation: 112
Yeah there's been people posting recently on various forums when trying to install GSB that it's broken.
 
Old 07-06-2012, 04:41 AM   #3
MadMaverick9
Member
 
Registered: Aug 2010
Location: Here
Distribution: Slackware 14.0
Posts: 118

Rep: Reputation: Disabled
This issue was first discussed here.

The problem is that lines that are not md5 checksums need to be properly commented with a "#".

The gsb checksums.md5 file as well as the slackware checksums.md5 file are not doing this.

Even though "md5sum" supports this since 2005.
 
Old 07-06-2012, 03:27 PM   #4
tallship
Member
 
Registered: Jul 2003
Location: On the Beaches of Super Sunny Southern San Clemente, California USA
Distribution: Slackware - duh!
Posts: 520
Blog Entries: 3

Rep: Reputation: 112Reputation: 112
Thumbs down

Like that really matters at all.

The fact is, people are posting that installation of GSB is broken, there's no clues there for users to correct the issue, and therefore people are posting such.
 
Old 07-09-2012, 08:28 PM   #5
Luiz Ramos
LQ Newbie
 
Registered: Jun 2010
Location: São Paulo - Brazil
Distribution: Slackware, Debian
Posts: 17

Original Poster
Rep: Reputation: 1
Some more information

Hello,

I found some more information. slapt-get doesn't seem to use md5sum as I thought first (and it's not a script). But it checks carefully the signature of CHECKSUMS.md5 with CHECKSUMS.md5.asc, and detects properly that the key is expired. What it doesn't do that perfect is to show it for the user... the message "not verified" spans to a couple of reasons, including "key expired".

So,

- md5sum is okay
- slapt-get is okay
- the file CHECKSUMS.md5 from GSB should be signed again with a valid signature
- slapt-get complains about that expired key from GSB and the signature released with that key

This solves the questions proposed in my first post. I would also suggest slapt-get could be more precise when showing the reason for the "not verified" status of the signature; I prepared mysqlf a first patch to do it, but this may break "apt-get" similarity, and for this reason I am not confident it would be accepted without discussion.

Thanks,

Luiz
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[GSB 3.0] Oh No! something has gone wrong! nmesis Slackware 6 09-18-2011 12:33 PM
Gbrainy without GSB? Gavin Harper Slackware 2 08-19-2010 05:50 AM
GSB 2.28 and GSB 2.30 (Release Candidate) now available for Slackware(64) 13.1 fidesratio Slackware 15 06-03-2010 02:12 AM
GSB several problems slayeriq Slackware 16 01-26-2009 04:51 PM
GSB v GWare mazebane Slackware 3 04-25-2005 02:11 AM


All times are GMT -5. The time now is 01:19 PM.

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration