Thread: [Bashburn-info] DANGER, DANGER Will Robinson... we have a big issue
Brought to you by:
bashburn
Menu
▾
▴
bashburn-info
|
From: Nick W. <ni...@uk...> - 2008-09-02 13:00:27
|
By chance I found a serious error.
I changed language and saved, closed and restarted BB. It squinnies a
lot and throws out all sorts of errors.
I then found my ~/.bashburnrc file was EMPTY, and BB couldn't create a
new one so I removed it out the way.
Reverting to r 481 now shows:
There is no '/home/nick/.bashburnrc'.
This is the file where BashBurn stores and reads its configuration.
I will now attempt to create one.
/usr/bin/bashburn: line 5: /usr/bin/BashBurn: Is a directory
Failed to create config file. This should not happen.
Please report this bug to the BashBurn developers.
Reverting to r 480 gets me back again and .bashburnrc is created with
defaults (but no menus bug, of course).
SOOOO, it looks like if you change something the .bashburnrc file gets
trashed, and BB cannot then write out a new one... {bonk}
If .bashburnrc already exists, you do not see this issue.
So move your .bashburnrc out the way and start BB.
Nick
--
Free Software Foundation Associate Member 5508
|
|
From: Nick W. <ni...@uk...> - 2008-09-02 13:12:56
|
On Tue, 2 Sep 2008 14:00:32 +0100
Nick Warne <ni...@uk...> wrote:
> By chance I found a serious error.
>
> I changed language and saved, closed and restarted BB. It squinnies a
> lot and throws out all sorts of errors.
>
> I then found my ~/.bashburnrc file was EMPTY, and BB couldn't create a
> new one so I removed it out the way.
>
> Reverting to r 481 now shows:
>
> There is no '/home/nick/.bashburnrc'.
> This is the file where BashBurn stores and reads its configuration.
> I will now attempt to create one.
> /usr/bin/bashburn: line 5: /usr/bin/BashBurn: Is a directory
> Failed to create config file. This should not happen.
> Please report this bug to the BashBurn developers.
>
> Reverting to r 480 gets me back again and .bashburnrc is created with
> defaults (but no menus bug, of course).
>
> SOOOO, it looks like if you change something the .bashburnrc file gets
> trashed, and BB cannot then write out a new one... {bonk}
>
> If .bashburnrc already exists, you do not see this issue.
>
> So move your .bashburnrc out the way and start BB.
>
> Nick
OK, fixed. Committed.
Nick
--
Free Software Foundation Associate Member 5508
|
|
From: Nick W. <ni...@uk...> - 2008-09-02 13:17:18
|
On Tue, 2 Sep 2008 14:12:59 +0100
Nick Warne <ni...@uk...> wrote:
> > SOOOO, it looks like if you change something the .bashburnrc file
> > gets trashed, and BB cannot then write out a new one... {bonk}
> >
> > If .bashburnrc already exists, you do not see this issue.
> >
> > So move your .bashburnrc out the way and start BB.
> >
> > Nick
>
> OK, fixed. Committed.
Not fixed :-( .bashburnrc doesn't keep changes now. At least I can
start it :-)
Nick
--
Free Software Foundation Associate Member 5508
|
|
From: Nick W. <ni...@uk...> - 2008-09-02 14:35:01
|
On Tue, 2 Sep 2008 14:17:26 +0100
Nick Warne <ni...@uk...> wrote:
> On Tue, 2 Sep 2008 14:12:59 +0100
> Nick Warne <ni...@uk...> wrote:
>
> > > SOOOO, it looks like if you change something the .bashburnrc file
> > > gets trashed, and BB cannot then write out a new one... {bonk}
> > >
> > > If .bashburnrc already exists, you do not see this issue.
> > >
> > > So move your .bashburnrc out the way and start BB.
> > >
> > > Nick
> >
> > OK, fixed. Committed.
>
> Not fixed :-( .bashburnrc doesn't keep changes now. At least I can
> start it :-)
OK, fixed now. Committed.
BTW, should the bbtempfile be created in the directory where the user
starts BB? Should it not be in /tmp/ ?
Nick
--
Free Software Foundation Associate Member 5508
|
|
From: Steven W. O. <st...@sy...> - 2008-09-02 15:23:42
|
On Tuesday, Sep 2nd 2008 at 10:35 -0000, quoth Nick Warne:
=>On Tue, 2 Sep 2008 14:17:26 +0100
=>Nick Warne <ni...@uk...> wrote:
=>
=>> On Tue, 2 Sep 2008 14:12:59 +0100
=>> Nick Warne <ni...@uk...> wrote:
=>>
=>> > > SOOOO, it looks like if you change something the .bashburnrc file
=>> > > gets trashed, and BB cannot then write out a new one... {bonk}
=>> > >
=>> > > If .bashburnrc already exists, you do not see this issue.
=>> > >
=>> > > So move your .bashburnrc out the way and start BB.
=>> > >
=>> > > Nick
=>> >
=>> > OK, fixed. Committed.
=>>
=>> Not fixed :-( .bashburnrc doesn't keep changes now. At least I can
=>> start it :-)
=>
=>OK, fixed now. Committed.
=>
=>BTW, should the bbtempfile be created in the directory where the user
=>starts BB? Should it not be in /tmp/ ?
It could be in /tmp but it really doesn't matter:
1. We cp then rm instead of mv. If we did an mv then we might have to
worry if the directory that the tmpfile was in was in a different
partition than the current dir.
2. The size of the file is measured in O(<1k) so it doesn't matter from
that end either.
The important thing is that mktemp should actually be given a template for
what the file should be called. If there's a problem that needs to be
debugged, then we know which file to look at.
--
Time flies like the wind. Fruit flies like a banana. Stranger things have .0.
happened but none stranger than this. Does your driver's license say Organ ..0
Donor?Black holes are where God divided by zero. Listen to me! We are all- 000
individuals! What if this weren't a hypothetical question?
steveo at syslang.net
|
|
From: Nick W. <ni...@uk...> - 2008-09-02 15:35:10
|
On Tue, 2 Sep 2008 11:23:50 -0400 (EDT) "Steven W. Orr" <st...@sy...> wrote: > It could be in /tmp but it really doesn't matter: > > 1. We cp then rm instead of mv. If we did an mv then we might have to > worry if the directory that the tmpfile was in was in a different > partition than the current dir. > > 2. The size of the file is measured in O(<1k) so it doesn't matter > from that end either. > > The important thing is that mktemp should actually be given a > template for what the file should be called. If there's a problem > that needs to be debugged, then we know which file to look at. OK, I see. BTW, can you please explain what you done here? In config/apply_options.sh There is: typeset bbtempfile=$(mktemp) and later... bbtempfile=$(mktemp bashburn_apply_opts.XXXXXX) Isn't the first assignment redundant? Nick -- Free Software Foundation Associate Member 5508 |
|
From: Steven W. O. <st...@sy...> - 2008-09-02 16:11:30
|
On Tuesday, Sep 2nd 2008 at 11:35 -0000, quoth Nick Warne: =>BTW, can you please explain what you done here? => =>In config/apply_options.sh => =>There is: => =>typeset bbtempfile=$(mktemp) => =>and later... => =>bbtempfile=$(mktemp bashburn_apply_opts.XXXXXX) => =>Isn't the first assignment redundant? Not redundant, just wrong. :-) I just fixed it. Thanks. -- Time flies like the wind. Fruit flies like a banana. Stranger things have .0. happened but none stranger than this. Does your driver's license say Organ ..0 Donor?Black holes are where God divided by zero. Listen to me! We are all- 000 individuals! What if this weren't a hypothetical question? steveo at syslang.net |
Thanks for helping keep SourceForge clean.
X