Re: [GitHub] [openoffice-org] Pilot-Pirx commented on pull request #3: Characters with accent are missing

2021-01-03 Thread Leonard Fogli
Ok

El dom., 3 de enero de 2021 5:19 p. m., GitBox  escribió:

>
> Pilot-Pirx commented on pull request #3:
> URL:
> https://github.com/apache/openoffice-org/pull/3#issuecomment-753690953
>
>
>You could do that for the other pages as well...
>
>
> 
> This is an automated message from the Apache Git Service.
> To respond to the message, please log on to GitHub and use the
> URL above to go to the specific comment.
>
> For queries about this service, please contact Infrastructure at:
> us...@infra.apache.org
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>


Re: Documenting what I'm learning

2021-01-03 Thread Leonard Fogli
Ok

El dom., 3 de enero de 2021 5:21 p. m., Patricia Shanahan 
escribió:

> Health permitting I may be able to help with this. I used to help develop,
> test, and debug multiprocessor servers so I have spent a lot of time
> thinking about concurrency correctness and performance.
>
> Patricia
>
> > On Dec 30, 2020, at 17:02, Steve Lubbs  wrote:
> >
> > Hi All,
> >
> > I've been spending quite a bit of time reverse engineering the threading
> and concurrency implementation and with an eye towards possible errors. I'm
> documenting what I find as I go with the hope that it'll be useful to
> others as well as myself. I'm not a UML expert by a long shot but I think I
> can use it well enough so it'll be useful.
> >
> > So if you don't here from me for a while it's not because I've left. I
> just have my head down.
> >
> > BTW, I'm going to see if Umbrello is useful for this.
> >
> > Steve Lubbs
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>


Re: [lazy consensus] Addition in release notes because of Big Sur (was: How should we proceed with BigSur?)

2021-01-03 Thread Leonard Fogli
Ok

El dom., 3 de enero de 2021 5:27 p. m., Patricia Shanahan 
escribió:

>
>
> > On Dec 27, 2020, at 10:30, Dave Fisher  wrote:
> >
> > 
> >
> >>> On Dec 27, 2020, at 5:13 AM, Patricia Shanahan  wrote:
> >>>
> >>>
>  On Dec 27, 2020, at 04:39, Jörg Schmidt 
> wrote:
> >>>
> >>> 
> 
>  -Original Message-
>  From: Peter Kovacs [mailto:pe...@apache.org]
>  Sent: Sunday, December 27, 2020 12:50 PM
>  To: dev@openoffice.apache.org
>  Subject: Re: [lazy consensus] Addition in release notes
>  because of Big Sur (was: How should we proceed with BigSur?)
> 
>  How about we make a blog post instead?
> 
>  We can describe
> 
>  What the impact is.
> 
>  What Versions are affected.
> 
>  Where our research is.
> 
>  And what our plans are.
> >>>
> >>> you mean in: https://blogs.apache.org? If so, I would find that even
> better.
> >>>
> >>> But who can do that? I myself do not feel able to do it because:
> >>> -my english is too bad for longer text
> >>
> >> If you do know the content for longer writing I may be able to help
> with editing. I am a native speaker of the English dialect of English and
> have near native reading, writing, and listening skills in the US dialect,
> which I would use for an AOO blog.
> >
> > The proposed text is now in Confluence. (Thanks Jörg!) I’ve made many
> edits.
> >
> > Here it is:
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173080814
> <
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173080814
> >
>
> It looks good to me for grammar and spelling.
>
> >
> > Regards,
> > Dave
> >
> >>
> >>
> >>> -I hardly know anything about technical backgrounds
> >>>
> >>> If I suggested an entry in the release notes it was because:
> >>> -I think it is valuable for the users to get an info as soon as
> possible
> >>> -I feel able to formulate a short English text for the Release Notes
> >>>
> >>>
> >>> I thus gladly support your suggestion of a blog post.
> >>>
> >>> If there is nothing clear in the next few hours I will, however, after
> the deadline of my proposal, state that "lazy consensus" has failed (in my
> opinion) and I will reintroduce the same proposal by way of formal
> "consensus building".
> >>>
> >>>
> >>>
> >>> greetings,
> >>> Jörg
> >>>
> >>>
> >>>
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> >>> For additional commands, e-mail: dev-h...@openoffice.apache.org
> >>>
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> >> For additional commands, e-mail: dev-h...@openoffice.apache.org
> >>
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>


Re: AOO 4.1.9 Info

2021-01-03 Thread Leonard Fogli
Emuybien. Exelete

El sáb., 2 de enero de 2021 2:00 p. m., Dave Fisher 
escribió:

>
>
> Sent from my iPhone
>
> > On Jan 2, 2021, at 11:43 AM, Keith N. McKenna 
> wrote:
> >
> > On 1/2/2021 11:07 AM, Matthias Seidel wrote:
> >> Hi Keith,
> >>
> >>> Am 31.12.20 um 04:43 schrieb Keith N. McKenna:
> >>> On 12/30/2020 7:17 PM, Matthias Seidel wrote:
>  Hi Keith,
> 
>  Just did a quick test with AOO 4.1.9 on Windows 7.
> 
>  Clipboard works as expected for me.
> 
>  Regarding the locked files, did you edit bootstrap.ini after "setup
> /a"
> >>> No simply did setup /a and it installed it with the profile in the same
> >>> folder.
> >> That may be the problem, you have to change the bootstrap.ini, otherwise
> >> you use the wrong AOO profile.
>  I will do some more tests (next year) with multi install on Windows
> 10.
> >>> Thank you Matthias. I will boot up my old windows 7 machine and try
> >>> testing it there as sell
> >>
> >> I now tested on Windows 10 with multiple AOO installations (4.1.8,
> >> 4.1.9, 4.2.0) and could not see a regression.
> >>
> >> @all: Maybe some other can also test? I don't feel comfortable if we are
> >> only two persons...
> >>
> >> Regards,
> >>
> >>Matthias
> >>
> >>>
> > Changing bootstrap.ini did the track and all problems disappeared. What
> > I do not understand is why. Leaving bootstrap.ini as is should just
> > point it to the standard profile
>
> Could it be because this is a Developer Build?
>
> Regards,
> Dave
>
> >
> >>> Regards
> >>> Keith
> >>>
>  Regards,
> 
> Matthias
> 
>  Am 31.12.20 um 00:59 schrieb Keith N. McKenna:
> > On 12/28/2020 5:11 AM, Matthias Seidel wrote:
> >> Hi all,
> >>
> >> Am 27.12.20 um 14:49 schrieb Jim Jagielski:
> >>> The AOO419 branch has been created.
> >>> The version numbers, et.al. have been bumped.
> >>> The Release Status page has been cloned:
> https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.9
> >> First test builds for Windows are available at:
> >>
> >> https://home.apache.org/~mseidel/AOO-builds/AOO-419-Test/
> >>
> >> Regards,
> >>
> >>Matthias
> >>
> >>>
> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> >>> For additional commands, e-mail: dev-h...@openoffice.apache.org
> >>>
> >> Attached is my QA report for 4.1.9 based on Matthias's 2020-12-29. I
> > would appreciate someone checking the issues I point out as I have
> been
> > experiencing occasional oddities with my system of late.
> >
> > Regards
> > Keith
> >>>
> >>
> >
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>


Re: AOO 4.1.9 Info

2021-01-03 Thread Keith N. McKenna
.
 That may be the problem, you have to change the bootstrap.ini, otherwise
 you use the wrong AOO profile.
>> I will do some more tests (next year) with multi install on Windows 10.
> Thank you Matthias. I will boot up my old windows 7 machine and try
> testing it there as sell
 I now tested on Windows 10 with multiple AOO installations (4.1.8,
 4.1.9, 4.2.0) and could not see a regression.

 @all: Maybe some other can also test? I don't feel comfortable if we are
 only two persons...

 Regards,

Matthias

>>> Changing bootstrap.ini did the track and all problems disappeared. What
>>> I do not understand is why. Leaving bootstrap.ini as is should just
>>> point it to the standard profile

After changing bootstrap.ini all problems initially reported are gone.
Attached is my updated QA report.

Regards
Keith


Verification_Report.odt
Description: application/vnd.oasis.opendocument.text


signature.asc
Description: OpenPGP digital signature


Re: [lazy consensus] Addition in release notes because of Big Sur (was: How should we proceed with BigSur?)

2021-01-03 Thread Patricia Shanahan



> On Dec 27, 2020, at 10:30, Dave Fisher  wrote:
> 
> 
> 
>>> On Dec 27, 2020, at 5:13 AM, Patricia Shanahan  wrote:
>>> 
>>> 
 On Dec 27, 2020, at 04:39, Jörg Schmidt  wrote:
>>> 
>>> 
 
 -Original Message-
 From: Peter Kovacs [mailto:pe...@apache.org] 
 Sent: Sunday, December 27, 2020 12:50 PM
 To: dev@openoffice.apache.org
 Subject: Re: [lazy consensus] Addition in release notes 
 because of Big Sur (was: How should we proceed with BigSur?)
 
 How about we make a blog post instead?
 
 We can describe
 
 What the impact is.
 
 What Versions are affected.
 
 Where our research is.
 
 And what our plans are.
>>> 
>>> you mean in: https://blogs.apache.org? If so, I would find that even better.
>>> 
>>> But who can do that? I myself do not feel able to do it because:
>>> -my english is too bad for longer text
>> 
>> If you do know the content for longer writing I may be able to help with 
>> editing. I am a native speaker of the English dialect of English and have 
>> near native reading, writing, and listening skills in the US dialect, which 
>> I would use for an AOO blog.
> 
> The proposed text is now in Confluence. (Thanks Jörg!) I’ve made many edits.
> 
> Here it is: 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173080814 
> 

It looks good to me for grammar and spelling. 

> 
> Regards,
> Dave
> 
>> 
>> 
>>> -I hardly know anything about technical backgrounds
>>> 
>>> If I suggested an entry in the release notes it was because:
>>> -I think it is valuable for the users to get an info as soon as possible
>>> -I feel able to formulate a short English text for the Release Notes
>>> 
>>> 
>>> I thus gladly support your suggestion of a blog post.
>>> 
>>> If there is nothing clear in the next few hours I will, however, after the 
>>> deadline of my proposal, state that "lazy consensus" has failed (in my 
>>> opinion) and I will reintroduce the same proposal by way of formal 
>>> "consensus building".
>>> 
>>> 
>>> 
>>> greetings,
>>> Jörg
>>> 
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>> 
> 

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: Documenting what I'm learning

2021-01-03 Thread Patricia Shanahan
Health permitting I may be able to help with this. I used to help develop, 
test, and debug multiprocessor servers so I have spent a lot of time thinking 
about concurrency correctness and performance. 

Patricia

> On Dec 30, 2020, at 17:02, Steve Lubbs  wrote:
> 
> Hi All,
> 
> I've been spending quite a bit of time reverse engineering the threading and 
> concurrency implementation and with an eye towards possible errors. I'm 
> documenting what I find as I go with the hope that it'll be useful to others 
> as well as myself. I'm not a UML expert by a long shot but I think I can use 
> it well enough so it'll be useful.
> 
> So if you don't here from me for a while it's not because I've left. I just 
> have my head down.
> 
> BTW, I'm going to see if Umbrello is useful for this.
> 
> Steve Lubbs
> 

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



[GitHub] [openoffice-org] Pilot-Pirx commented on pull request #3: Characters with accent are missing

2021-01-03 Thread GitBox


Pilot-Pirx commented on pull request #3:
URL: https://github.com/apache/openoffice-org/pull/3#issuecomment-753690953


   You could do that for the other pages as well...



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: [openoffice] branch trunk updated: 'fakeroot' is no longer optional, but required, when making deb/dpkg so no need to worry about the old hack and seeing if we have fakeroot.

2021-01-03 Thread Carl Marcum

Just FYI that I just built trunk on Ubuntu 18.04 with:

$ ./configure \
--with-system-stdlibs \
--enable-category-b \
--enable-beanshell \
--enable-wiki-publisher \
--enable-bundled-dictionaries \
--enable-dbus  \
--without-junit \
--without-stlport \
--with-package-format="installed" \
--with-dmake-url=https://github.com/jimjag/dmake/archive/v4.13.1/dmake-4.13.1.tar.gz 
\

--with-epm-url=https://github.com/jimjag/epm/archive/v5.0.0/epm-5.0.0.tar.gz

and was able to start it up fine.

For some reason I can't use --enable-gstreamer
(libgstreamer1.0-0, -dev, and -dbg are installed)
or --enable-opengl
libopengl0 is installed (don't see a -dev library available)

But that's probably for another thread. Only noted here as a difference.

Best regards,
Carl

On 1/3/21 10:22 AM, Jim Jagielski wrote:

Followed up on the bugz ticket...


On Jan 3, 2021, at 9:16 AM, Matthias Seidel  wrote:

Hi Jim,

One user has a problem with this commit, see:

https://bz.apache.org/ooo/show_bug.cgi?id=128422

Could you have a look?

Regards,

Matthias




-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org




-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: Proposed change for download page

2021-01-03 Thread Rory O'Farrell
On Sun, 3 Jan 2021 21:24:06 +0100
Matthias Seidel  wrote:

> Hi Marcus,
> 
> Am 03.01.21 um 20:07 schrieb Marcus:
> >
> > I've added a bit more magic:
> >
> > https://openoffice-org.staged.apache.org/download/index.html
> >
> > Now we can show a different text when Windows, Mac or Linux install
> > files are selected. It's a short title with more text as mouse-over.
> >
> > For Linux it's known. However, for Windows and Mac we need the info we
> > want to show the users.
> >
> > Suggestions?
> 
> Thanks! That looks good!
> 
> For Windows I would suggest as title:
> 
> Additional notes for Windows!
> 
> Text:
> 
> At the moment we only offer a 32-bit (x86) version for Windows.
> However, this version installs and runs also on Windows 64-bit (x86-64).
> Please note that you may need JAVA in 32-bit for additional functionality.

Add: which must then be selected (one time only) in /Tools /Options /OpenOffice 
/Java


Rory

> 
> Maybe the wording can be enhanced...
> 
> Regards,
> 
>    Matthias
> 
> >
> > Thanks to all for helping.
> >
> > Marcus
> >
> 


-- 
Rory O'Farrell 

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: Proposed change for download page

2021-01-03 Thread Matthias Seidel
Hi Marcus,

Am 03.01.21 um 20:07 schrieb Marcus:
>
> I've added a bit more magic:
>
> https://openoffice-org.staged.apache.org/download/index.html
>
> Now we can show a different text when Windows, Mac or Linux install
> files are selected. It's a short title with more text as mouse-over.
>
> For Linux it's known. However, for Windows and Mac we need the info we
> want to show the users.
>
> Suggestions?

Thanks! That looks good!

For Windows I would suggest as title:

Additional notes for Windows!

Text:

At the moment we only offer a 32-bit (x86) version for Windows.
However, this version installs and runs also on Windows 64-bit (x86-64).
Please note that you may need JAVA in 32-bit for additional functionality.

Maybe the wording can be enhanced...

Regards,

   Matthias

>
> Thanks to all for helping.
>
> Marcus
>



smime.p7s
Description: S/MIME Cryptographic Signature


Re: Proposed change for download page

2021-01-03 Thread Marcus

Am 31.12.20 um 11:50 schrieb Matthias Seidel:

Am 31.12.20 um 11:41 schrieb Marcus:

Am 31.12.20 um 01:01 schrieb Matthias Seidel:

Am 31.12.20 um 00:46 schrieb Marcus:

As I haven't seen any veto-like negative statement the change is now
online.

However, any changes are still possible.


I would propose that we add some additional text for Windows and macOS.
It could be done similar to Linux (DEB vs. RPM). Maybe we could make the
color a bit more visible?

This would allow us to tell people that the Windows 32-bit version is
also suitable for Windows 64-bit and that the macOS version >= 10.7 also
runs with macOS Big Sur on Apple M1 chips.


yes, that was also my idea. And the reason for my question via PM. ;-)
But of course we can also extended this trick to the Mac users.

As we see, a lot of users don't know about Rosetta 2. And until we have
a "Universal Binary" we should give them a hint.


Unfortunatelly, we need to add (and translate) these new strings to
every download page.


Yes, I would proceed like we did it with the Linux notes:

Add the strings (in English) to every download page and let the
translation teams translate.
This is much easier now with Git(Hub).

If a language is unmaintained, the strings will remain in English until
someone volunteers to translate them.


I've added a bit more magic:

https://openoffice-org.staged.apache.org/download/index.html

Now we can show a different text when Windows, Mac or Linux install 
files are selected. It's a short title with more text as mouse-over.


For Linux it's known. However, for Windows and Mac we need the info we 
want to show the users.


Suggestions?

Thanks to all for helping.

Marcus




Am 30.12.20 um 00:18 schrieb Marcus:

Am 29.12.20 um 20:05 schrieb Dave Fisher:

On Dec 29, 2020, at 10:47 AM, Czesław Wolański
 wrote:


I suggest we offer something clearer and more direct. I’m not sure
what

that is.

Perhaps we need a compatible java page to point Windows, macOS,
and Linux

users

to acceptable versions.
Maybe we have such a page we can better highlight from the
Download page?


Link on the download page "Java and Apache OpenOffice"

https://www.openoffice.org/download/common/java.html

Page with sections:
-  "Why Do I Need Java to Use Apache OpenOffice?",
-  "Which Java Version Do I Need to Use Apache OpenOffice?"
-  "Where Can I Get Java?".

Is that a good starting point?


I think so. That page could use a major edit. We don’t need to
discuss legacy releases and the links need to be more direct.


+1


For Oracle looks best: https://java.com/en/download/manual.jsp


And instead of OpenJDK we should point to AdoptOpenJDK:
https://adoptopenjdk.net/releases.html


It looks like we could even add a button to the download page that
might pick out the proper adoptopenjdk.


Even this is possible. But it takes time as the download style and
JavaScript magic needs to be extended.

Until then the simple "Windows 32-bit (x86) (EXE)" drop-down-item is
a good and clear statement to separate from 64-bit.

I can also add a 64-bit item with a hint text that AOO 32-bit will
run also on Windows 64-bit and I can also add a Java hint.

Marcus




Am Di., 29. Dez. 2020 um 19:02 Uhr schrieb Dave Fisher
:

On Dec 29, 2020, at 9:47 AM, Rory O'Farrell 
wrote:
On Tue, 29 Dec 2020 18:31:23 +0100
Peter Kovacs  wrote:

On 29.12.20 18:25, Dave Fisher wrote:

On Dec 29, 2020, at 8:39 AM, Jörg Schmidt


wrote:



-Original Message-
From: Bidouille [mailto:ooofo...@free.fr]
Sent: Tuesday, December 29, 2020 3:02 PM
To: dev@openoffice.apache.org
Subject: Re: Proposed change for download page


Personally, I don't see the need until we have a real x64
version.

+1

Don't you care if users can't find their way around and
therefore

stop using AOO?


That was exactly the result of the thread that prompted me to
suggest

a small correction on the download page.


The thread is unfortunately in German, but here is the link:
http://de.openoffice.info/viewtopic.php?p=293070#p293070

You should have started your discussion with this context.

It is better to discuss the actual problem which is that
Windows users

of AOO don’t know that they require a 32 bit Java than it is to
suggest a
minor fix to the download page.

Java 32 bit is part of the release notes.


Which, experience on en-Forum indicates, no average user ever
reads!


Does your average Windows user know the difference between X86 and
X64?!

I suggest we offer something clearer and more direct. I’m not sure
what
that is. Perhaps we need a compatible java page to point Windows,
macOS,
and Linux users to acceptable versions. Maybe we have such a page
we can
better highlight from the Download page?

What advice does the en-Forum offer?



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.

[GitHub] [openoffice] cbmarcum opened a new pull request #115: Flaky tests

2021-01-03 Thread GitBox


cbmarcum opened a new pull request #115:
URL: https://github.com/apache/openoffice/pull/115


   This work is for flaky BVT tests that randomly pass or fail during multiple 
runs against the same build.
   Basically I'm adding a thread sleep prior to the test assertion check.
   So far this has reduced the average failure count of 2 or 3 per run to 0 for 
the last 5 runs I've made against trunk.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: [openoffice] branch trunk updated: 'fakeroot' is no longer optional, but required, when making deb/dpkg so no need to worry about the old hack and seeing if we have fakeroot.

2021-01-03 Thread Jim Jagielski
Followed up on the bugz ticket...

> On Jan 3, 2021, at 9:16 AM, Matthias Seidel  
> wrote:
> 
> Hi Jim,
> 
> One user has a problem with this commit, see:
> 
> https://bz.apache.org/ooo/show_bug.cgi?id=128422
> 
> Could you have a look?
> 
> Regards,
> 
>Matthias
> 
> 


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: [openoffice] branch trunk updated: 'fakeroot' is no longer optional, but required, when making deb/dpkg so no need to worry about the old hack and seeing if we have fakeroot.

2021-01-03 Thread Matthias Seidel
Hi Jim,

One user has a problem with this commit, see:

https://bz.apache.org/ooo/show_bug.cgi?id=128422

Could you have a look?

Regards,

   Matthias


Am 30.12.20 um 17:07 schrieb j...@apache.org:
> This is an automated email from the ASF dual-hosted git repository.
>
> jim pushed a commit to branch trunk
> in repository https://gitbox.apache.org/repos/asf/openoffice.git
>
>
> The following commit(s) were added to refs/heads/trunk by this push:
>  new 49cc844  'fakeroot' is no longer optional, but required, when making 
> deb/dpkg so no need to worry about the old hack and seeing if we have 
> fakeroot.
> 49cc844 is described below
>
> commit 49cc8443e2aaa7c02ddd1611e7be852fd90266a6
> Author: Jim Jagielski 
> AuthorDate: Wed Dec 30 11:06:33 2020 -0500
>
> 'fakeroot' is no longer optional, but required, when making deb/dpkg
> so no need to worry about the old hack and seeing if we have
> fakeroot.
> ---
>  main/solenv/bin/modules/installer/download.pm | 24 +++-
>  main/solenv/bin/modules/installer/epmfile.pm  | 27 
> ---
>  main/solenv/bin/modules/installer/worker.pm   | 16 ++--
>  main/sysui/desktop/debian/makefile.mk | 10 ++
>  4 files changed, 11 insertions(+), 66 deletions(-)
>
> diff --git a/main/solenv/bin/modules/installer/download.pm 
> b/main/solenv/bin/modules/installer/download.pm
> index 573d546..05f9237 100644
> --- a/main/solenv/bin/modules/installer/download.pm
> +++ b/main/solenv/bin/modules/installer/download.pm
> @@ -302,13 +302,7 @@ sub tar_package
>  {
>   my ( $installdir, $tarfilename, $getuidlibrary) = @_;
>  
> - my $ldpreloadstring = "";
> -
> - if (($ENV{'FAKEROOT'} ne "no") && ($ENV{'FAKEROOT'} ne "")) {
> - $ldpreloadstring = $ENV{'FAKEROOT'};
> - } else {
> - if ( $getuidlibrary ne "" ) { $ldpreloadstring = "LD_PRELOAD=" 
> . $getuidlibrary; }
> - }
> + my $ldpreloadstring = $ENV{'FAKEROOT'};
>  
>   my $systemcall = "cd $installdir; $ldpreloadstring tar -cf - * > 
> $tarfilename";
>   
> @@ -373,13 +367,7 @@ sub create_tar_gz_file_from_package
>   my $targzname = $packagename . 
> $installer::globals::downloadfileextension;
>   $installer::globals::downloadfilename = $targzname;
>  
> - my $ldpreloadstring = "";
> -
> - if (($ENV{'FAKEROOT'} ne "no") && ($ENV{'FAKEROOT'} ne "")) {
> - $ldpreloadstring = $ENV{'FAKEROOT'};
> - } else {
> - if ( $getuidlibrary ne "" ) { $ldpreloadstring = "LD_PRELOAD=" 
> . $getuidlibrary; }
> - }
> + my $ldpreloadstring = $ENV{'FAKEROOT'};
>  
>   my $systemcall = "cd $installdir; $ldpreloadstring tar -cf - 
> $packagename | gzip > $targzname";
>   $installer::logger::Info->printf("... %s ...\n", $systemcall);
> @@ -798,13 +786,7 @@ sub create_tar_gz_file_from_directory
>   my $changedir = $installdir;
>   installer::pathanalyzer::get_path_from_fullqualifiedname(\$changedir);
>  
> - my $ldpreloadstring = "";
> -
> - if (($ENV{'FAKEROOT'} ne "no") && ($ENV{'FAKEROOT'} ne "")) {
> - $ldpreloadstring = $ENV{'FAKEROOT'};
> - } else {
> - if ( $getuidlibrary ne "" ) { $ldpreloadstring = "LD_PRELOAD=" 
> . $getuidlibrary; }
> - }
> + my $ldpreloadstring = $ENV{'FAKEROOT'};
>  
>   $installer::globals::downloadfileextension = ".tar.gz";
>   $installer::globals::downloadfilename = $downloadfilename . 
> $installer::globals::downloadfileextension;
> diff --git a/main/solenv/bin/modules/installer/epmfile.pm 
> b/main/solenv/bin/modules/installer/epmfile.pm
> index c7f9860..d33ffcd 100644
> --- a/main/solenv/bin/modules/installer/epmfile.pm
> +++ b/main/solenv/bin/modules/installer/epmfile.pm
> @@ -885,26 +885,7 @@ sub set_patch_state
>  
>  sub get_ld_preload_string
>  {
> - my ($includepatharrayref) = @_;
> -
> - my $getuidlibraryname = "getuid.so";
> -
> - my $ldpreloadstring;
> -
> - my $getuidlibraryref = 
> installer::scriptitems::get_sourcepath_from_filename_and_includepath(\$getuidlibraryname,
>  $includepatharrayref, 0);
> -
> - if (($ENV{'FAKEROOT'} ne "no") && ($ENV{'FAKEROOT'} ne "")) {
> -
> - $ldpreloadstring = $ENV{'FAKEROOT'};
> -
> - } else {
> -
> - if ($$getuidlibraryref eq "") { 
> installer::exiter::exit_program("ERROR: Could not find $getuidlibraryname!", 
> "get_ld_preload_string"); }
> -
> - my $ldpreloadstring = "LD_PRELOAD=" . $$getuidlibraryref;
> - }
> - 
> - return $ldpreloadstring;
> + return $ENV{'FAKEROOT'};
>  }
>  
>  #
> @@ -926,15 +907,15 @@ sub call_epm
>   my $outdirstring = "";
>   if ( $installer::globals::epmoutpath ne "" ) { $outdirstring = " 
> --output-dir $installer::globals::epmoutpath"; }
>   
> - # Debian package build needs fakeroot or our LD_PRELOAD hack for 
> correct rights
> + # Debian package build n