[SOLVED] BunsenLabs Updates for Software

Horizon_Brave · 2016-02-26 17:07:44

Hey everyone, I understand the procedures more for the updating process for debian in regards to software updates. But what about our own mini distro BunsenLabs? If we find an error in something like the bl-welcome script for example... (just randomly picked something specific to B.L)

1.What is the process that *we* use to push this out to users?

2.BunsenLabs doesn't have branches of development really, so if we make changes to scripts or code that is in use in BL, do we just post it up on github, and tell people to update their repos and they can download it immediately?

3. Does updating individual software/scripts like this, effect or change our version numbers (IE do we increment the 8.3 to like 8.3.01 if we update one of our scripts/code?

Thanks everyone!

Last edited by Horizon_Brave (2016-02-27 21:57:14)

damo · 2016-02-26 21:53:10

One of the packaging boys may chime in here, but in the meantime here is my understanding:

ATM there are no development branches, but if for instance I wanted to make changes to `bl-welcome` I would make one on github. After due consideration and approval this could be merged with the master branch. Anyone else could fork the repo and do their own development, which potentially could be merged with the master at some point.

The netinstall update script should package the latest master commits from github, instead of whatever is in the bunsen repos.

When "we" get round to it, a github repo is packaged, and the version is bumped, so the next update/upgrade will bring the new version in. Debian package version numbering is explained here

Horizon_Brave · 2016-02-26 23:20:36

damo wrote:

One of the packaging boys may chime in here, but in the meantime here is my understanding:
ATM there are no development branches, but if for instance I wanted to make changes to `bl-welcome` I would make one on github. After due consideration and approval this could be merged with the master branch. Anyone else could fork the repo and do their own development, which potentially could be merged with the master at some point.
The netinstall update script should package the latest master commits from github, instead of whatever is in the bunsen repos.
When "we" get round to it, a github repo is packaged, and the version is bumped, so the next update/upgrade will bring the new version in. Debian package version numbering is explained here

Ah, make sense. My only question is that if the fix is something that is more immediate. And you all don't want to wait until you have multiple packages ready to be updated, you want to update 1 single script, perhaps for security reason, or if it breaks something else in a bad way...how does that work? Is the script to be updated, pushed through and the entire process? Or is it the netinstall update that you talked about, that is more for quick immediate fixes like this?

damo · 2016-02-26 23:31:45

The netinstall script is for installing BL on top of a Debian netinstall. It was originally developed to get a system up and running, before we had a package repo. It gets its sources from github and creates debs on your machine, which are then installed. You can then update stuff which is newer than the previous build, without having to rebuild the whole lot (a deb still has to built and installed though).

If there was an urgent fix that needed doing, then the repo package would be made, with a bumped version number, so you can apt-get update/upgrade it. I presume an announcement would be made on the forums if there were any updates to BL packages after a full release.

Don't forget that this won't update $USER's configs, which would need to be done manually.

Horizon_Brave · 2016-02-26 23:37:25

I also notice that in the netinstall github page there's this line:

"There is also a script: bl-github-upgrade
which can be run to upgrade the BunsenLabs packages
from the GitHub repository in order to get the latest versions."

bl-github-upgrade: script to upgrade the BunsenLabs packages

I guess in short, what I'm asking, is that, if there's only like 1 package or script that needs an immediate dire fix, what is the process to get it out and available to everyone as soon as possible? And because we want our users to have non-buggy software, how would we go about make sure everyone applies that new update? (not everyone runs daily update/upgrades)

Horizon_Brave · 2016-02-26 23:39:08

damo wrote:

The netinstall script is for installing BL on top of a Debian netinstall. It was originally developed to get a system up and running, before we had a package repo. It gets its sources from github and creates debs on your machine, which are then installed. You can then update stuff which is newer than the previous build, without having to rebuild the whole lot (a deb still has to built and installed though).
If there was an urgent fix that needed doing, then the repo package would be made, with a bumped version number, so you can apt-get update/upgrade it. I presume an announcement would be made on the forums if there were any updates to BL packages after a full release.
Don't forget that this won't update $USER's configs, which would need to be done manually.

Look at that, you answered my questions before I asked Thanks Damo!! Understood

damo · 2016-02-26 23:43:31

Horizon_Brave wrote:

.... how would we go about make sure everyone applies that new update? (not everyone runs daily update/upgrades)

Impossible! You have to let users of a "tweakers" distro look after themselves to a large extent, IMO. And the day we have a package auto-update feature configured by default..........is the day I install Win10

Horizon_Brave · 2016-02-27 21:56:18

Once again another case solved. Thanks Damo.

hhh · 2016-02-28 00:51:32

Horizon_Brave wrote:

Hey everyone, I understand the procedures more for the updating process for debian in regards to software updates. But what about our own mini distro BunsenLabs? If we find an error in something like the bl-welcome script for example... (just randomly picked something specific to B.L)

Post a bug report here on the forums and we'll take care of it. The only time you might want to push a GitHub commit is if you have a fix already, and even then a bug report with the fix in the post would be better.

d4rksenl4bs · 2016-03-09 20:29:30

is there any reason why u guys chose openbox... and not blackbox or fluxbox..just wondering

Last edited by d4rksenl4bs (2016-03-09 20:32:29)

damo · 2016-03-09 21:42:49

d4rksenl4bs wrote:

is there any reason why u guys chose openbox... and not blackbox or fluxbox..just wondering

Crunchbang Waldorf used Openbox; BunsenLabs is the community continuation of CB, which used many OB-specific configs; BL=Debian Stable+Openbox.

...and I prefer Openbox over any other WM, so I would fight tooth-and-nail for it to be the BL default

d4rksenl4bs · 2016-03-10 17:24:16

im all for it guys can i get copy of ure source list i messd mine up ...plus do any of y seen pentesting repos for bl...icant remember where saw it.... but anyways thx

damo · 2016-03-10 17:37:15

@d4rksenl4bs
Please try not to ask Off-Topic questions in a thread marked [SOLVED]. The sources.list entries have been posted many times in the forums, so try a search. (Maybe we should post it as a sticky topic, since the question comes up a lot)

Also, although I don't want to sound like a boring old mod, would you take some time to read the Forum rules about posting style?

Forum Rules wrote:

Posting style guide
Try to use good grammar and spelling, and make your contributions as concise as possible. Remember that English is not the first language of many members.

d4rksenl4bs · 2016-03-10 23:18:14

my bad ...im kinda new to forums...i mean i usually read this prob my 2nd forum acount ever ..so im tryin tho..and yeah right after that post i found.. its just iit got dupliccated...most of em none free so how they supose to worrk

damo · 2016-03-11 02:01:38

d4rksenl4bs wrote:

my bad ...im kinda new to forums...i mean i usually read this prob my 2nd forum acount ever ..so im tryin tho..and yeah right after that post i found.. its just iit got dupliccated...most of em none free so how they supose to worrk

Huh??? If you don't slow down a bit, and write understandable english, then you will miss out on a lot of help. I think many members won't bother trying to translate sloppy posts

Forum Rules wrote:

Posting style guide
Try to use good grammar and spelling, and make your contributions as concise as possible. Remember that English is not the first language of many members.

#1 2016-02-26 17:07:44

[SOLVED] BunsenLabs Updates for Software

#2 2016-02-26 21:53:10

Re: [SOLVED] BunsenLabs Updates for Software

#3 2016-02-26 23:20:36

Re: [SOLVED] BunsenLabs Updates for Software

#4 2016-02-26 23:31:45

Re: [SOLVED] BunsenLabs Updates for Software

#5 2016-02-26 23:37:25

Re: [SOLVED] BunsenLabs Updates for Software

#6 2016-02-26 23:39:08

Re: [SOLVED] BunsenLabs Updates for Software

#7 2016-02-26 23:43:31

Re: [SOLVED] BunsenLabs Updates for Software

#8 2016-02-27 21:56:18

Re: [SOLVED] BunsenLabs Updates for Software

#9 2016-02-28 00:51:32

Re: [SOLVED] BunsenLabs Updates for Software

#10 2016-03-09 20:29:30

Re: [SOLVED] BunsenLabs Updates for Software

#11 2016-03-09 21:42:49

Re: [SOLVED] BunsenLabs Updates for Software

#12 2016-03-10 17:24:16

Re: [SOLVED] BunsenLabs Updates for Software

#13 2016-03-10 17:37:15

Re: [SOLVED] BunsenLabs Updates for Software

#14 2016-03-10 23:18:14

Re: [SOLVED] BunsenLabs Updates for Software

#15 2016-03-11 02:01:38

Re: [SOLVED] BunsenLabs Updates for Software

Board footer