Hello Sam, Even with the freedom changes is there not a way to make the source changes and then help automate the process of generating all the files needed for the repository? Perhaps there is just too much variation between packages.
Do you know of a link to a decent primer on how to use pbuilder? Also as a reminder I suggest sending a notification to DistroWatch about 4. They have the status of gNewSense as dormant. Dennis On Wed, 2016-05-04 at 23:21 +0200, Sam Geeraerts wrote: > Op Tue, 03 May 2016 19:36:09 -0400 > schreef dww <[email protected]>: > > > Were you able to solve the build problem with Iceweasel? > > I'm afraid not. I hope the mipsel builds will go smoother with gNewSense > 5, but I doubt it. > > > It would be nice if some how we can automate the process of freeing > > those packages but I guess it is practically impossible to avoid the > > manual work. On the other hand that is probably the main set of tasks > > in getting 5 out anyway? Let me know when work on 5 starts. > > Finding out what needs to be modified and how can't be automated. What > can/should be automated is merging upstream changes when Debian does a > (security) update for a package. > > _______________________________________________ > gNewSense-dev mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/gnewsense-dev _______________________________________________ gNewSense-dev mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/gnewsense-dev
