Oolite Bulletins

For information and discussion about Oolite.
It is currently Sat Jul 22, 2017 12:46 pm

All times are UTC




Post new topic  Reply to topic  [ 9 posts ] 
Author Message
PostPosted: Tue Jul 28, 2015 10:38 am 
Offline
Retired Assassin
Retired Assassin
User avatar

Joined: Thu Aug 12, 2004 4:54 pm
Posts: 1739
Location: Belgium
Soo.. I'm running testing, some days ago did a fresh install on a second laptop and to my surprise when I wanted to give Oolite a spin, it was not in the repositories (!)



it was REMOVED from testing on July 11th...:

https://tracker.debian.org/news/697003

Reasons:

https://tracker.debian.org/pkg/oolite


Last edited by Getafix on Mon Sep 14, 2015 7:48 am, edited 2 times in total.
Marked as "Solved"


Top
   
PostPosted: Tue Jul 28, 2015 10:41 am 
Offline
Sharp Shooter Spam Assassin
Sharp Shooter Spam Assassin
User avatar

Joined: Sat Jul 04, 2009 9:31 pm
Posts: 12654
Location: Corke's Drift
That's Oolite 1.77 they're talking about, yes?

_________________
The only good fnord is a dead fnord!


Top
   
PostPosted: Tue Jul 28, 2015 10:43 am 
Offline
Retired Assassin
Retired Assassin
User avatar

Joined: Thu Aug 12, 2004 4:54 pm
Posts: 1739
Location: Belgium
I thought the most up to date in the repos last time I checked was 1.76-ish, so I guess, yes...

(EDIT: yes, yes indeed)


Top
   
PostPosted: Tue Jul 28, 2015 10:44 am 
Offline
Sharp Shooter Spam Assassin
Sharp Shooter Spam Assassin
User avatar

Joined: Sat Jul 04, 2009 9:31 pm
Posts: 12654
Location: Corke's Drift
Tell 'em to put Oolite 1.82 in there. <grins> How are you, btw?

_________________
The only good fnord is a dead fnord!


Last edited by Cody on Tue Jul 28, 2015 10:56 am, edited 1 time in total.

Top
   
PostPosted: Tue Jul 28, 2015 10:54 am 
Offline
Retired Assassin
Retired Assassin
User avatar

Joined: Thu Aug 12, 2004 4:54 pm
Posts: 1739
Location: Belgium
Quote:
Tell 'em to put Oolite 1.82 in there. <grins> How are you, btw?
:lol: Hi Cody, I was thinking the same thing, but do not recognize the name of the maintainer...

I am... Hard to tell how I am, life's a bit of a challenge (P.M. because I don't feel like telling the world what's happening in our family)


Top
   
PostPosted: Tue Jul 28, 2015 2:57 pm 
Offline
---- E L I T E ----
---- E L I T E ----
User avatar

Joined: Mon Apr 06, 2009 12:20 pm
Posts: 6178
Location: Aboard the Pitviper S.E. "Blackwidow"
Quote:
Summary of problems follows:
Quote:
Found in version oolite/1.77.1-3

The license header contains a short name with a space, which does not conform to the specification.
* png license (paragraph at line 121)
* variant of apache 1.0 (paragraph at line 89)

The package fails to build in a test rebuild on at least amd64 with
gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9.

Identifier: timestamps_from_cpp_macros
URL https://wiki.debian.org/ReproducibleBui ... mCPPMacros
Description The C pre-processor macros `__DATE__`, `__TIME__`, and `__TIMESTAMP__`
captures the current time, and thus will obviously make a build
unreproducible.

Maintainers for oolite are Nicolas Boulenguez <nicolas@debian.org>.

_________________
Most games have some sort of paddling-pool-and-water-wings beginning to ease you in: Oolite takes the rather more Darwinian approach of heaving you straight into the ocean, often with a brick or two in your pockets for luck. ~ Disembodied


Top
   
PostPosted: Tue Jul 28, 2015 4:02 pm 
Offline
Commodore
Commodore
User avatar

Joined: Thu Nov 07, 2013 10:21 pm
Posts: 281
I couldn't find __TIME__ or __TIMESTAMP__ in trunk, and the only __DATE__ I could find (other than one reference in the Mac code) was in setting the date for the window title. I'm pretty sure they could change that in their version if they really wanted to.

The other bug I noticed was https://bugs.debian.org/cgi-bin/bugrepo ... bug=778039, which claims we're using formatting strings in a potentially unsafe way. Fixing that would involve replacing e.g. kOOLogNoteFuelLeak with the actual string it represents throughout the code.

EDIT: I'm talking rubbish on that last point (not an unusual occurrence). It's the second argument that's the problem - apparently, printf("string") is unsafe - you're supposed to use something like printf("%s", "string") instead. It might also be complaining that we're sending an NSString object instead of a literal C string.


Top
   
PostPosted: Tue Jul 28, 2015 4:43 pm 
Offline
Quite Grand Sub-Admiral
Quite Grand Sub-Admiral
User avatar

Joined: Fri Nov 11, 2011 6:19 pm
Posts: 4007
Quote:
EDIT: I'm talking rubbish on that last point (not an unusual occurrence). It's the second argument that's the problem - apparently, printf("string") is unsafe - you're supposed to use something like printf("%s", "string") instead. It might also be complaining that we're sending an NSString object instead of a literal C string.
printf("string") is probably fine, but printf(stringVariable) isn't.

Adding -Werror=format-security to a gcc 4.9 build of the current master doesn't give any errors, so it's possible that they wouldn't even get that error if they tried to build 1.82

_________________
OXPs: [EliteWiki] New Cargoes, [EliteWiki] Skilled NPCs, [EliteWiki] Curse of the Black Sunspot, and more


Top
   
PostPosted: Fri Sep 11, 2015 4:29 pm 
Offline
Retired Assassin
Retired Assassin
User avatar

Joined: Thu Aug 12, 2004 4:54 pm
Posts: 1739
Location: Belgium
Oolite 1.82-1 migrated to testing :-)

https://tracker.debian.org/news/709957 6 days in unstable, no showstoppers
Migrated to testing: https://tracker.debian.org/news/711851


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic  [ 9 posts ] 

All times are UTC


Who is online

Users browsing this forum: No registered users and 3 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
cron
Powered by phpBB® Forum Software © phpBB Limited