Discussion:
[Gnewsense-dev] Question about gNewSense 5 (Debian Stretch)
Wellton
2017-04-11 12:43:38 UTC
Permalink
Hello Everybody,

Any possibility of doing gNewSense 5 based on Debian Stretch and not in
the Jessie?

att
GREen MOnster Games
2017-04-11 14:49:54 UTC
Permalink
Any possibility of doing gNewSense 5 based on Debian Stretch and not in the
Jessie?
I hope too for that. I have asked about the script-tools to modify
gNewSense but the developers only wrote me the old script when It was
ubuntu based.
I am like you or other person that want help and support this project,
but the developers must understand that, must learn that.

I have saw other topic, I feel that they don't want more help for this
project, because if they want them, it's normal that change the
pubblic scripts and reply about the serious questions.

I have wrote 5 times, only a reply I have received without the best explain.

If one person is smart it's easy to understand that need help to make
a new build or test the new release. It's a stupid things, because is
one little project with an group really little to support it. It's a
shame, really.

-_-
Paul Boddie
2017-04-11 15:13:32 UTC
Permalink
Post by GREen MOnster Games
Post by Wellton
Any possibility of doing gNewSense 5 based on Debian Stretch and not in
the Jessie?
I hope too for that. I have asked about the script-tools to modify
gNewSense but the developers only wrote me the old script when It was
ubuntu based.
I am like you or other person that want help and support this project,
but the developers must understand that, must learn that.
I agree with you on this.

It looks like the action takes place here:

http://bzr.savannah.gnu.org/lh/gnewsense/

Meanwhile, the gnewsense.org site is still super-slow to access, or actually
inaccessible for me at this moment, and yet a static page was deployed as the
front page of that site because of supposed (but unspecified) performance
problems with the wiki. That makes me wonder whether the actual performance
problems weren't more fundamental to the virtual hosting being used, despite
claims that the FSF infrastructure people would have noticed such problems and
flagged them.

Anyway, if things were a bit more transparent and distributed, people could at
least figure out some of the simple stuff for themselves and make modest
contributions. I still don't really know where to begin, and so I just decide
to spend my time on other things instead.

Paul
GREen MOnster Games
2017-04-13 15:38:10 UTC
Permalink
Post by Paul Boddie
I agree with you on this.
http://bzr.savannah.gnu.org/lh/gnewsense/
I see that every day to verify the update. But the really big problem
are the new scripts.
Those 2 developers don't upload the new scripts to modify one debian
based. If they want that others testers and developers want
participate They must upload those scripts.

This is a really stupid thing but really important for this little project. ===
=================xx Organization, communication and transparency.
Post by Paul Boddie
Meanwhile, the gnewsense.org site is still super-slow to access, or actually
inaccessible for me at this moment, and yet a static page was deployed as the
front page of that site because of supposed (but unspecified) performance
problems with the wiki. That makes me wonder whether the actual performance
problems weren't more fundamental to the virtual hosting being used, despite
claims that the FSF infrastructure people would have noticed such problems and
flagged them.
Yes I allow all that you are explained me. More times too I have said
the same. 3 years the website is really slow without solution. Exist
more and more ways to do better. For example wordpress, plone and
drupal.

Thi group now have not many Volunteers because for this situation.

I am using gNewSense from 6 years a go, for me it's an really nice
operating system, but or the developers listen us or nothing.

I want collaborate like you, we are here if those 2 developers want
upload the scripts.

It's a best idea to organize the work for Debian Stretch based.


Now the team must explain 4 points:

1. The uploading the new scripts to build the new release.

2. The access to collaborate. I am interested too for that.

3. The collaboration to write a new website. Drupal, wordpress, plone
or more more more more more more other.

4. The name of developers active now. Because we need the contact to
collaborate better.

and plus one point 5. The name of Volunteers that translate the languages.
Post by Paul Boddie
Anyway, if things were a bit more transparent and distributed, people could at
least figure out some of the simple stuff for themselves and make modest
contributions. I still don't really know where to begin, and so I just decide
to spend my time on other things instead.
I too Paul, now I have wrote the points that the team must clear and
explain and than we can collaborate too on this beautiful project, but
now we are not more volunteers I think this is one good alarm for make
better. This is the last possibility.


Thanks in advance

MIKE from Green Monster Games Team
Post by Paul Boddie
Paul
Sam Geeraerts
2017-04-17 21:03:04 UTC
Permalink
Op Thu, 13 Apr 2017 17:38:10 +0200
Post by GREen MOnster Games
4. The name of developers active now. Because we need the contact to
collaborate better.
Eddi and me. Although activity has been very low (again) recently due
to ongoing priorities/deadlines unrelated to gNewSense.

I've updated the list of members [1] to reflect currently active or
interested people (who were already a member) for as far as I'm aware.
Post by GREen MOnster Games
1. The uploading the new scripts to build the new release.
The builder_lordeddie branch has the most recent work. @eddi: if that's
not true, please speak up.
Post by GREen MOnster Games
2. The access to collaborate. I am interested too for that.
Great. Read access to the code is open to all, so anyone can study the
code, obviously a prerequisite to contribute patches. Questions and
patches can be sent to the -dev mailing list, which is open to all. (I
know that responsiveness is an issue, see further.) You can also apply
for membership on Savannah. I was once hesitant to approve, because
Savannah has no way to limit write access to VCS. I'm more lenient now,
commits should be double checked anyhow.

I don't give access to the servers easily. I hope you agree that needs
a high level of trust.
Post by GREen MOnster Games
3. The collaboration to write a new website. Drupal, wordpress, plone
or more more more more more more other.
I still think the problem is not with Moinmoin itself. I'd like to take
a different approach to tackle the issue. There are currently 24955
pages and 43272 users in the wiki. I'd first like to get rid of all
users who have never edited anything. If there's not already a script
that does that, it will have to be written.
Post by GREen MOnster Games
and plus one point 5. The name of Volunteers that translate the languages.
I think nobody's actively translating now.
Post by GREen MOnster Games
Post by Paul Boddie
Anyway, if things were a bit more transparent and distributed,
people could at least figure out some of the simple stuff for
themselves and make modest contributions. I still don't really know
where to begin, and so I just decide to spend my time on other
things instead.
Being transparent means better communication. I'm going to think of a
way to manage my time to do that. The think is that when I reply on the
mailing list I want to do it properly. So I want to take enough time
and get a clear head. Often both are lacking at the end of the day when
I have all other stuff out of the way, so I end up postponing my
replying, sometimes way too long. I need to dedicate some time for
this, if maybe only once a week. That wouldn't be super responsive, but
it's better than leaving things linger indefinitely.

I'm not sure what being more distributed would mean for the project.

[1] https://savannah.nongnu.org/project/memberlist.php?group=gnewsense

Regards,
Sam
GREen MOnster Games
2017-04-18 03:00:50 UTC
Permalink
Also Sam first I must say many thanks for you answer. I have really
appreciated it.
Post by Sam Geeraerts
not true, please speak up.
Yes Rhys McBurnie (sir123) has me explained.

But to install the builder and configure all

I must only type: --------Checkout builder


bzr branch http://bzr.savannah.gnu.org/lh/gnewsense/builder_lordeddi

and than

cd builder

And

Step 3: Configuration?

and

Step 4: Debmirror?

Step 5: Packages?

Step 6: Setting up $REPODST?

Step 7: Generate the repository?

tep 8: Generate the LiveCD

./gen-livecd

The created image will be placed in
$LIVECDDIR/$DISTRONAME_L-livecd-$RELEASE-$ARCHTOBUILD-$LIVECD_VERSION.iso

./gen-cdsource
./stage-cd

Step 9: Push your repository to a mirror and publicise

You can now publish your repository (the dists and pool) directories
as well as your LiveCD to your mirror and publicise your new
distribution to the world.

./push-repo
./push-cd

Because I have not the further informations from the official webite.
There only the instructions about the old script.
Post by Sam Geeraerts
Great. Read access to the code is open to all, so anyone can study the
code, obviously a prerequisite to contribute patches. Questions and
patches can be sent to the -dev mailing list, which is open to all. (I
know that responsiveness is an issue, see further.) You can also apply
for membership on Savannah. I was once hesitant to approve, because
Savannah has no way to limit write access to VCS. I'm more lenient now,
commits should be double checked anyhow.
That's important yes. Step to step all is possible. Now i want
understand all to contribute with you.
If there are many info not clear I ask again. It's not problem.
Post by Sam Geeraerts
I don't give access to the servers easily. I hope you agree that needs
a high level of trust.
It's important to offer the trust for the new members. And than we can
work togheter. But the first is to see all tools to work togheter :)
Post by Sam Geeraerts
I still think the problem is not with Moinmoin itself. I'd like to take
a different approach to tackle the issue. There are currently 24955
pages and 43272 users in the wiki. I'd first like to get rid of all
users who have never edited anything. If there's not already a script
that does that, it will have to be written.
The website is slow. It's need to run to wait more minutes. Moinmoin
it's a beautiful cms but I think that the first problem can be from
the query, maybe this server has not more power and I have wrote my
opinion that drupal or wordpress there are the really nice alternative
for an small server. Maybe I can help with this problem too. But we
must see step by step.
Post by Sam Geeraerts
I think nobody's actively translating now.
That's bad without the volunteers to translate. We must search the new
translators, It's really important.
Post by Sam Geeraerts
I'm not sure what being more distributed would mean for the project.
[1] https://savannah.nongnu.org/project/memberlist.php?group=gnewsense
I have done the request for inclusion :) ------------)) GREMO (Mike)


Thanks in advance


Mike (GREMO) from Green Monster Games
Sam Geeraerts
2017-04-19 20:32:46 UTC
Permalink
Op Tue, 18 Apr 2017 05:00:50 +0200
Post by GREen MOnster Games
But to install the builder and configure all
Working on Builder itself is definitely necessary to go forward, but
perhaps an easier way to contribute is to focus on the gen-scripts. You
can hard code the variables (or even use wildcards, i.e. instead of
$VERSION) and run the script standalone. The gen scripts for packages
always follow the same pattern:

1) get source package
2) unpack
3) modify code
4) update changelog
5) build

Step 3 is the one that involves brain power.

If you want further information about Builder itself, I'll be happy to
oblige if you tell me where exactly you're stuck.

In the interest of transparency I can say that Eddi and I are going to
sit together some time next week to get work on Builder moving again.
We'll share the outcome on this list.
Post by GREen MOnster Games
The website is slow. It's need to run to wait more minutes. Moinmoin
it's a beautiful cms but I think that the first problem can be from
the query, maybe this server has not more power and I have wrote my
opinion that drupal or wordpress there are the really nice alternative
for an small server. Maybe I can help with this problem too. But we
must see step by step.
The website's been fairly responsive to me in the last few days. I've
updated the relevant bug report [1]. If anyone want to start on writing
some scripts, please let me know (here or in the bug report).
Post by GREen MOnster Games
Post by Sam Geeraerts
I think nobody's actively translating now.
That's bad without the volunteers to translate. We must search the new
translators, It's really important.
Maybe the past translators can be motivated to pick up where they left
off. Would you like to find and contact them about it? The Editor group
[2] might be a good place to start.

I have done the request for inclusion :) ------------)) GREMO (Mike)

Welcome to the team. :)

[1] https://savannah.nongnu.org/bugs/index.php?47898
[2] http://www.gnewsense.org/EditorGroup
Carlos Eduardo Díaz Peñuela
2017-04-19 22:45:52 UTC
Permalink
Hi guys, yo hablo español, I can help to translate some hours per week. :-)
Post by Sam Geeraerts
Op Tue, 18 Apr 2017 05:00:50 +0200
Post by GREen MOnster Games
But to install the builder and configure all
Working on Builder itself is definitely necessary to go forward, but
perhaps an easier way to contribute is to focus on the gen-scripts. You
can hard code the variables (or even use wildcards, i.e. instead of
$VERSION) and run the script standalone. The gen scripts for packages
1) get source package
2) unpack
3) modify code
4) update changelog
5) build
Step 3 is the one that involves brain power.
If you want further information about Builder itself, I'll be happy to
oblige if you tell me where exactly you're stuck.
In the interest of transparency I can say that Eddi and I are going to
sit together some time next week to get work on Builder moving again.
We'll share the outcome on this list.
Post by GREen MOnster Games
The website is slow. It's need to run to wait more minutes. Moinmoin
it's a beautiful cms but I think that the first problem can be from
the query, maybe this server has not more power and I have wrote my
opinion that drupal or wordpress there are the really nice alternative
for an small server. Maybe I can help with this problem too. But we
must see step by step.
The website's been fairly responsive to me in the last few days. I've
updated the relevant bug report [1]. If anyone want to start on writing
some scripts, please let me know (here or in the bug report).
Post by GREen MOnster Games
Post by Sam Geeraerts
I think nobody's actively translating now.
That's bad without the volunteers to translate. We must search the new
translators, It's really important.
Maybe the past translators can be motivated to pick up where they left
off. Would you like to find and contact them about it? The Editor group
[2] might be a good place to start.
I have done the request for inclusion :) ------------)) GREMO (Mike)
Welcome to the team. :)
[1] https://savannah.nongnu.org/bugs/index.php?47898
[2] http://www.gnewsense.org/EditorGroup
_______________________________________________
gNewSense-dev mailing list
https://lists.nongnu.org/mailman/listinfo/gnewsense-dev
--
Carlos Eduardo Díaz Peñuela
Ingeniero de Sistemas y Computación
Maestría en Tecnología Informática
Universidad Pedagógica y Tecnológica de Colombia
m: 3124809893
a: Calle 48 # 3-77
w: pandora.tk e: ***@gmail.com
Sam Geeraerts
2017-04-22 18:11:38 UTC
Permalink
Op Wed, 19 Apr 2017 17:45:52 -0500
schreef Carlos Eduardo Díaz Peñuela
Post by Carlos Eduardo Díaz Peñuela
Hi guys, yo hablo español, I can help to translate some hours per week. :-)
Super! These are some relevant wiki pages for translators:

http://www.gnewsense.org/Processes/TranslatingTheWebsite
http://www.gnewsense.org/TranslationTeam
GREen MOnster Games
2017-04-22 18:07:02 UTC
Permalink
Mike from Green Monster Games Crew-- greenmonstergames.wordpress.com

*Free or Libre Software Enthusiast
**Slackware Enthusiast
*** Recycling Enthusiast
****The DIY Enthusiast



for Sam
Post by Sam Geeraerts
Post by GREen MOnster Games
But to install the builder and configure all
Working on Builder itself is definitely necessary to go forward, but
perhaps an easier way to contribute is to focus on the gen-scripts. You
can hard code the variables (or even use wildcards, i.e. instead of
$VERSION) and run the script standalone. The gen scripts for packages
1) get source package
2) unpack
3) modify code
4) update changelog
5) build
Step 3 is the one that involves brain power.
Ok. Thanks
Post by Sam Geeraerts
In the interest of transparency I can say that Eddi and I are going to
sit together some time next week to get work on Builder moving again.
We'll share the outcome on this list.
Ok I wait your update with Eddi and than i will take the ask about
this tutorial's script. Because If I want make an new script there are
not many comment inside the source code. I wait that you and Eddi will
do better from this update and I will propose the ask about me with
those steps.
Post by Sam Geeraerts
Maybe the past translators can be motivated to pick up where they left
off. Would you like to find and contact them about it? The Editor group
[2] might be a good place to start.
I can try to search some volunteer. I hope that I can found.
Post by Sam Geeraerts
I have done the request for inclusion :) ------------)) GREMO (Mike)
Welcome to the team. :)
Thanks Buddy :)


For Paul
You can try to fix this bugs about this website maybe we can make too
a good solution.

For Carlos Eduardo Diaz

Really nice if you want help to translate in espaniol eheh :D Muchas Gracias :)
Paul Boddie
2017-04-21 16:30:19 UTC
Permalink
Op Thu, 13 Apr 2017 17:38:10 +0200 schreef GREen MOnster Games
Post by GREen MOnster Games
3. The collaboration to write a new website. Drupal, wordpress, plone
or more more more more more more other.
I still think the problem is not with Moinmoin itself. I'd like to take
a different approach to tackle the issue. There are currently 24955
pages and 43272 users in the wiki. I'd first like to get rid of all
users who have never edited anything. If there's not already a script
that does that, it will have to be written.
I can probably dig up something either from the MoinMoin site or from scripts
I've written to delete users who register to try and spam but never manage to
perform edits.

I think Moin is a good-enough solution for the gNewSense site. Going off and
making another CMS or trying to shoehorn WordPress, Plone or Drupal into this
role is a colossal distraction that probably won't yield the hoped-for
benefits, anyway.

[...]
Being transparent means better communication. I'm going to think of a
way to manage my time to do that. The think is that when I reply on the
mailing list I want to do it properly. So I want to take enough time
and get a clear head. Often both are lacking at the end of the day when
I have all other stuff out of the way, so I end up postponing my
replying, sometimes way too long. I need to dedicate some time for
this, if maybe only once a week. That wouldn't be super responsive, but
it's better than leaving things linger indefinitely.
Is no-one getting any financial support for working on gNewSense, then? Is it
yet another case of "glory" supposedly being sufficient reward for everybody's
time and the impact on their health and quality of life?
I'm not sure what being more distributed would mean for the project.
[1] https://savannah.nongnu.org/project/memberlist.php?group=gnewsense
For me, I'd just appreciate a simple overview of how Debian's output is
transformed into gNewSense. It seems to me that everyone who knows how a
distribution is made is so embedded in the process that they never really care
about communicating how it is done. As far as I remember, the wiki had some
descriptions, but they were out-of-date and described the previous Ubuntu-
based approach.

Paul
Sam Geeraerts
2017-04-22 18:33:37 UTC
Permalink
Op Fri, 21 Apr 2017 18:30:19 +0200
Post by Paul Boddie
I can probably dig up something either from the MoinMoin site or from
scripts I've written to delete users who register to try and spam but
never manage to perform edits.
Excellent.
Post by Paul Boddie
I think Moin is a good-enough solution for the gNewSense site. Going
off and making another CMS or trying to shoehorn WordPress, Plone or
Drupal into this role is a colossal distraction that probably won't
yield the hoped-for benefits, anyway.
Seconded.
Post by Paul Boddie
Is no-one getting any financial support for working on gNewSense,
then? Is it yet another case of "glory" supposedly being sufficient
reward for everybody's time and the impact on their health and
quality of life?
I think I'm one of many who would like to get paid to work on free
software, but struggle to find a working business model. I'm sure some
people would like to make a donation for gNewSense, but that's unlikely
to add up to a steady income. So quitting the day job is not an option
and then donation wouldn't buy time. That's why I don't accept
donations at all.
Post by Paul Boddie
For me, I'd just appreciate a simple overview of how Debian's output
is transformed into gNewSense. It seems to me that everyone who knows
how a distribution is made is so embedded in the process that they
never really care about communicating how it is done. As far as I
remember, the wiki had some descriptions, but they were out-of-date
and described the previous Ubuntu- based approach.
The general idea is this:

1) Copy Debian's package repository.
2) Identify the packages that don't align with the Free Software
Distribution Guidelines or that contain Debian specific branding.
3) For each of those packages:
3a) Unpack the source
3b) Modify the code
3c) Update version info, changelog and other package metadata
3d) Repackage source and build binaries
4) Replace those packages in the package repository
5) Build installer images

Builder is a tool that knows about repo locations, branding info,
packages to be modified, build instructions etc.
Paul Boddie
2017-04-22 19:05:11 UTC
Permalink
Post by Sam Geeraerts
Post by Paul Boddie
I can probably dig up something either from the MoinMoin site or from
scripts I've written to delete users who register to try and spam but
never manage to perform edits.
Excellent.
I'll put a shell script together that should support pruning users from the
wiki. I did this for another wiki, but I don't think I have access to the
script any more.

[...]
Post by Sam Geeraerts
Post by Paul Boddie
Is no-one getting any financial support for working on gNewSense,
then? Is it yet another case of "glory" supposedly being sufficient
reward for everybody's time and the impact on their health and
quality of life?
I think I'm one of many who would like to get paid to work on free
software, but struggle to find a working business model. I'm sure some
people would like to make a donation for gNewSense, but that's unlikely
to add up to a steady income. So quitting the day job is not an option
and then donation wouldn't buy time. That's why I don't accept
donations at all.
I just wondered about this because for some organisations it is important to
have libre GNU/Linux distributions available, and yet the number of such
distributions seems to have fluctuated over the years, and their continued
availability has been uncertain. It probably isn't in anyone's best interests
for things to continue like this. While enthusiastic volunteers can always be
persuaded to spend their own time on it (for the "glory"), it just frustrates
and confuses people if those volunteers burn out, give up, and so on. And I
doubt that the FSF having to constantly evaluate new distributions is a great
use of their (volunteers') time.
Post by Sam Geeraerts
Post by Paul Boddie
For me, I'd just appreciate a simple overview of how Debian's output
is transformed into gNewSense. It seems to me that everyone who knows
how a distribution is made is so embedded in the process that they
never really care about communicating how it is done. As far as I
remember, the wiki had some descriptions, but they were out-of-date
and described the previous Ubuntu- based approach.
1) Copy Debian's package repository.
2) Identify the packages that don't align with the Free Software
Distribution Guidelines or that contain Debian specific branding.
3a) Unpack the source
3b) Modify the code
3c) Update version info, changelog and other package metadata
3d) Repackage source and build binaries
4) Replace those packages in the package repository
5) Build installer images
Builder is a tool that knows about repo locations, branding info,
packages to be modified, build instructions etc.
I saw once again that Devuan has been trying to make derivative distribution
building easier:

https://dev1galaxy.org/viewtopic.php?id=551
https://dev1galaxy.org/viewtopic.php?id=549

I don't know how much their tools overlap with the activities involved here,
though.

Paul
Paul Boddie
2017-04-23 17:53:31 UTC
Permalink
Post by Paul Boddie
I'll put a shell script together that should support pruning users from the
wiki. I did this for another wiki, but I don't think I have access to the
script any more.
Well, I rediscovered how to get access to the script and modified it to be
somewhat more general. It is attached to this message.

It's probably best to run it in an empty directory because it produces various
report files to indicate what it has discovered about wiki users. There is an
option that can then be used to move "bad" users out of the users directory.
The Moin documentation suggests that cached information may also need
updating, but the script doesn't do anything about that at present.

If you try running it, please let me know what it manages to do.

Paul
Sam Geeraerts
2017-04-28 21:32:19 UTC
Permalink
Op Sun, 23 Apr 2017 19:53:31 +0200
Post by Paul Boddie
Well, I rediscovered how to get access to the script and modified it
to be somewhat more general. It is attached to this message.
Am I right that this creates a list of users that have never edited?
Paul Boddie
2017-04-29 10:37:26 UTC
Permalink
Post by Sam Geeraerts
Op Sun, 23 Apr 2017 19:53:31 +0200
Post by Paul Boddie
Well, I rediscovered how to get access to the script and modified it
to be somewhat more general. It is attached to this message.
Am I right that this creates a list of users that have never edited?
Sorry, I should have provided some guidance! Effectively, you get a collection
of files, with the most important ones being these:

bad.txt should be a collection of users who never edited

bad-domains.txt should just summarise where the bad users came from (which
domains were used in their e-mail addresses)

The principal goal of this script is to prune users from the wiki who
registered in an attempt to spam the wiki and who managed to verify their e-
mail details, but who didn't get any further because of other measures in
place to prevent unwanted edits.

Although this might seem like an unlikely scenario, I imagine that it has
become more common to permit self-registration, mostly because that does save
administrators the effort of interacting with the account creation mechanisms,
but then to have explicit access control lists that grant specific users
editing privileges. Getting such privileges is a matter of interacting with
the community running the wiki and building up enough trust that an
administrator then updates the list with a new user's details, which is a
fairly simple action.

The other files are as follows:

accounts.txt should be a collection of e-mail address lines from account files

editors_migrated.txt are usernames of people whose content was imported into
the wiki (not really appropriate here, I guess, but you never know)

editors_wiki.txt are accounts of people who have edited the wiki

editors.txt combines the two sources of editors (using mapping.txt to map
usernames to identifiers)

Possibly, less interesting are the files that deal with people registering for
the wiki and having to verify their accounts over e-mail:

unverified.txt are accounts that still need to perform e-mail verification

verified.txt are accounts that do not need to perform e-mail verification

Generally, spammers are quite able to verify their accounts, so this is not a
sufficient measure to prevent spamming.

For your purposes, I would imagine that you would mostly be interested in just
removing spurious accounts, many of which could have been generated by
potential spammers. It might be interesting to monitor the rate of new account
creation. When the Mailman Wiki was migrated, we encountered such issues very
early on, but I haven't looked too closely at the situation since then.

So, running the script should just produce these files which you can then
inspect. If there are few bad users, things become a bit more involved in
terms of figuring out whether those users really can be removed - they could
be spammers that did manage to edit or they could be genuine editors - but
with many bad users, you would need to just "sanity check" the contents of the
file and see that the script really did do its job correctly.

I hope this is a bit more helpful!

Paul

Sam Geeraerts
2017-04-28 21:48:32 UTC
Permalink
Op Sat, 22 Apr 2017 21:05:11 +0200
Post by Paul Boddie
I just wondered about this because for some organisations it is
important to have libre GNU/Linux distributions available, and yet
the number of such distributions seems to have fluctuated over the
years, and their continued availability has been uncertain. It
probably isn't in anyone's best interests for things to continue like
this. While enthusiastic volunteers can always be persuaded to spend
their own time on it (for the "glory"), it just frustrates and
confuses people if those volunteers burn out, give up, and so on. And
I doubt that the FSF having to constantly evaluate new distributions
is a great use of their (volunteers') time.
I guess they now have some influence on it, since they employ one of
the libre distro maintainers (although in another role). Other than
that, there are no easy answers.
Post by Paul Boddie
I saw once again that Devuan has been trying to make derivative
https://dev1galaxy.org/viewtopic.php?id=551
https://dev1galaxy.org/viewtopic.php?id=549
The live cd docs will come in handy. Their packaging is similar to what
we did for Ucclia. But it doesn't explain how upstream updates are
processed. That was a manual process for Ucclia and thus a bottleneck.
It also doesn't explain what to do when the upstream package is not in
git. I suspect that would also need to be solved manually.

The nice thing about Builder is that it requires little manual
intervention once it's set up correctly.
GREen MOnster Games
2017-04-28 22:33:16 UTC
Permalink
Mike from Green Monster Games Crew-- greenmonstergames.wordpress.com

*Free or Libre Software Enthusiast
**Slackware Enthusiast
*** Recycling Enthusiast
****The DIY Enthusiast
Post by Sam Geeraerts
The live cd docs will come in handy. Their packaging is similar to what
we did for Ucclia. But it doesn't explain how upstream updates are
processed. That was a manual process for Ucclia and thus a bottleneck.
It also doesn't explain what to do when the upstream package is not in
git. I suspect that would also need to be solved manually.
It's not the same but is similar process, yes.
Post by Sam Geeraerts
The nice thing about Builder is that it requires little manual
intervention once it's set up correctly.
Yeah. I agree completely because with a good builder with one little
manual, we can have a good way to test the nexr releases and modify
togheter where is the bug or mistake , this is a great powerful, yeah,
absolutely :)
Loading...