Forum: >>> Magnum BBS <<<

lintian errors packaging Barry's Emacs

From Barry Scott@21:1/5 to All on Mon Dec 26 16:30:01 2022

I am build my first Debian package for Barry's Emacs (https:://barrys-emacs.org)
My build environment is Ubuntu 22.10.

There are some lintian errors that I do not know how to handler.

Now running lintian bemacs_8.9.3_amd64.changes ...
E: bemacs source: malformed-debian-changelog-version 8.9.3 (for non-native) [debian/changelog:1]
E: bemacs source: python3-depends-but-no-python3-helper bemacs
E: bemacs: python3-script-but-no-python3-dep /usr/bin/python3 (does not satisfy python3:any | python3-minimal:any) [usr/bin/bemacs]
E: bemacs: python3-script-but-no-python3-dep /usr/bin/python3 (does not satisfy python3:any | python3-minimal:any) [usr/bin/bemacs_server]
E: bemacs source: source-is-missing [HTML/extn_intro.html]
...
E: bemacs source: source-is-missing [HTML/ug_top.html]
Finished running lintian.

E: bemacs source: malformed-debian-changelog-version 8.9.3 (for non-native) [debian/changelog:1]

It seems that the changelog issue is around lintian mandating a issue to close? I have no issue what do I put in the changelog? Or do I have to configure this check off?

E: bemacs source: python3-depends-but-no-python3-helper bemacs

This seems to mean that I need something in the rules file to make lintian be happy.
My build system can set the shebang to what ever is expected. I have tried with /usr/bin/python3 and /usr/bin/python3.10 both get errors.

E: bemacs source: source-is-missing [HTML/extn_intro.html]

This I am baffled by. The named sources are in the bemacs_8.9.3.orig.tar.gz but this
error claims they are not present.

How do debug this?

Barry

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Santiago Vila@21:1/5 to All on Tue Dec 27 02:40:01 2022

El 26/12/22 a las 16:28, Barry Scott escribió:

E: bemacs source: malformed-debian-changelog-version 8.9.3 (for non-native) [debian/changelog:1]

It seems that the changelog issue is around lintian mandating a issue to close?
I have no issue what do I put in the changelog? Or do I have to configure this
check off?

It's not related to closing issues. Look at the error message: it says [debian/changelog:1] that the error happens in the very first line of the debian/changelog, probably you wrote something like this as the very first line:

bemacs (8.9.3) unstable; urgency=medium

This is only ok if you are creating a native package.

I assume your package is not native, so version should really be 8.9.3-1 for the first Debian revision, 8.9.3-2 for the second, and so on.

E: bemacs source: python3-depends-but-no-python3-helper bemacs

This seems to mean that I need something in the rules file to make lintian be happy.
My build system can set the shebang to what ever is expected. I have tried with
/usr/bin/python3 and /usr/bin/python3.10 both get errors.

Explanation here:

https://lintian.debian.org/tags/python3-depends-but-no-python3-helper

My advice here is to take a look at other Debian python packages.

E: bemacs source: source-is-missing [HTML/extn_intro.html]

This I am baffled by. The named sources are in the bemacs_8.9.3.orig.tar.gz but this
error claims they are not present.

Explanation here:

https://lintian.debian.org/tags/source-is-missing

Did you really write extn_intro.html by hand from scratch, or maybe you created it
from something else before putting it inside bemacs_8.9.3.orig.tar.gz?

Lintian thinks it's the latter, hence the complain. If it's really the former, use a lintian override.

Hope this helps.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Barry Scott@21:1/5 to Santiago Vila on Tue Dec 27 12:30:01 2022

On 27/12/2022 01:37, Santiago Vila wrote:

El 26/12/22 a las 16:28, Barry Scott escribió:

E: bemacs source: malformed-debian-changelog-version 8.9.3 (for
non-native) [debian/changelog:1]

It seems that the changelog issue is around lintian mandating a issue
to close?
I have no issue what do I put in the changelog? Or do I have to
configure this
check off?

It's not related to closing issues. Look at the error message: it says [debian/changelog:1] that the error happens in the very first line of
the debian/changelog, probably you wrote something like this as the
very first line:

bemacs (8.9.3) unstable; urgency=medium

This is only ok if you are creating a native package.
I assume your package is not native, so version should really be
8.9.3-1 for the first Debian revision, 8.9.3-2 for the second, and so on.

Your guess is correct I did not have a <debian-version> in the changelog.

I was going to ask where that was set.

E: bemacs source: python3-depends-but-no-python3-helper bemacs

This seems to mean that I need something in the rules file to make
lintian be happy.
My build system can set the shebang to what ever is expected. I have
tried with
/usr/bin/python3 and /usr/bin/python3.10 both get errors.

Explanation here:

https://lintian.debian.org/tags/python3-depends-but-no-python3-helper

My advice here is to take a look at other Debian python packages.

Happy to do that but I do not know how to go from a package like
python3-brotli and find its source to read.

I found https://sources.debian.org/ but I've failed to track down that
package. I tried a couple of packages to hunt for.

How do I go from a installed package and find its debian source?

I'm guessing that I need to add a call to something, a macro expansion
maybe
that I can use in my build logic. When I do that I assume that lintian
will be
happy that I did things right in the build.

E: bemacs source: source-is-missing [HTML/extn_intro.html]

This I am baffled by. The named sources are in the
bemacs_8.9.3.orig.tar.gz but this
error claims they are not present.

Explanation here:

https://lintian.debian.org/tags/source-is-missing

I read this and found myself none the wiser. It says this:
"The source of the following file is missing. Lintian checked a few
possible paths to find the source, and did not find it."

No where does it say that lintian is assuming that
the file is the result of machine generation from source that is not
in the package.

Did you really write extn_intro.html by hand from scratch, or maybe
you created it
from something else before putting it inside bemacs_8.9.3.orig.tar.gz?

Yes I hand write HTML. FYI the original versions of these files is very
old 30+ years ago
and predate markdown etc.

Lintian thinks it's the latter, hence the complain. If it's really the former,
use a lintian override.

I figured out the override to silence the error.

Barry

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Ole Streicher@21:1/5 to Barry Scott on Tue Dec 27 12:40:01 2022

Hi Barry,

Barry Scott <[email protected]> writes:

I am build my first Debian package for Barry's Emacs (https:://barrys-emacs.org)

Aside from Santiagos technical tips: If you really want to contribute
your package to the Debian distribution, you should also have a few
other things in mind:

* Your package should come with a proper DFGS compliant [1] license. Your
Github upstream package [2] doesn't have one, and it would be useful
(not only for Debian packaging) to add one there.

* I would recommend to follow the usual procedures here. Specifically,
you should open an "Intend To Package" (ITP) bug [3] to indicate your
packaging efforts.

* The target distribution for the packaging is "unstable" (sid). From
there it migrates to the Debian distribution. It also migrates to
Ubuntu, Mint, and all the other derivative distributions.

* The packaging efforts should be separated from the software
development itself and usually happens on the Salsa Gitlab server
[4]. I'd strongly recommend to allow team maintainance, to lower the
barrier of packaging-related contributions.

Best regards

Ole

[1] https://www.debian.org/social_contract#guidelines
https://wiki.debian.org/DFSGLicenses
[2] https://github.com/barry-scott/BarrysEmacs
[3] https://wiki.debian.org/ITP
[4] https://salsa.debian.org

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Santiago Vila@21:1/5 to All on Tue Dec 27 13:10:01 2022

El 27/12/22 a las 12:28, Barry Scott escribió:

How do I go from a installed package and find its debian source?

On a Debian/Ubuntu system, if you have deb-src lines in your /etc/apt/sources.list,
then

apt-get source source-package-name

will retrieve the source and unpack it automatically.

If you don't have deb-src lines, they are the same as the usual deb lines except that they begin with deb-src. For example, I have this in a sid
chroot used to build packages:

deb http://deb.debian.org/debian sid main contrib non-free
deb-src http://deb.debian.org/debian sid main contrib non-free

Hope this helps.

Note: As explained by Ole, if your program is libre, it is in the
best interest of everyone that you try to package it for Debian,
not just for yourself.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From The Wanderer@21:1/5 to Ole Streicher on Tue Dec 27 13:50:01 2022

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
On 2022-12-27 at 07:12, Ole Streicher wrote:

Hi Santiago,

Santiago Vila <[email protected]> writes:

If you don't have deb-src lines, they are the same as the usual deb
lines except that they begin with deb-src.

Just curious: why are the deb line not used by default here?

As a place to look for source-package information in the absence of
deb-src lines, you mean?

While I have no inside knowledge on this, my inference has always been
that it's to avoid downloading (and updating) and storing the index data
for source packages, for that presumed large majority of people who have
no need to care about source packages. I.e., the act of adding a deb-src
line is the way for the sysadmin to denote "for this computer, having convenient access to Debian source packages is sufficiently important
that the cost of the index data - in local storage, in network traffic,
and in remote-server transmission load - is worth paying".

In principle it would probably be possible to design a way of flagging
that in reverse (so that deb lines would get both types of index by
default, and only if a flag is set would the source-package idex data
not be gotten), but just at a glance that looks like it'd be more
complicated to engineer, and in any case the transition seems as if it'd
be mildly horrific.

--
The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEJCOqsZEc2qVC44pUBKk1jTQoMmsFAmOq6CgACgkQBKk1jTQo MmsxxQ//UvdDep6KXJKpcwgF3KuMObNfR9dfy3E8eUKBvj3IE6X3T2WydljbK6TR k+ZoOjLPoqWcxySjEFrIDjH1oVb/LoamkVR7zQbWYs2EDnptQWoIw5ENAgi/L6ZE 0axZ8Q+e/F1iBFpali5k8/QAzfu6bhGq/5YTAd0NsUXi7fO/+HBXVmcdqHBl431O QQgbDkeqWTwNckhmHf7Hplrqa40FO78w4nFnp050k/ONCIatkM/4rX8OW2inzrbE KgnXVaif1fhjwC+IJah6Lfap/ApCzRPZxHuyNOu9nwU1Ug2MKpNXyhTuzoewgLz4 XX3VTW91IIQU4a2WMsRCIb8AlQJhD2/RY1dMwdlJfaghbkh8ZS0GrksJtVbR5suT 0tj0dhoXr0Me6aJa2YWUPhukyi4zJwIqhpoDB7SMj4P6Yj6clwbmHR3vxj9oGsdg j50PXhnDAro1yBx5ztHvl/lguOhw3ypqnu7183YVhmbXA8nBA+aqc5Iup3bLo0Bq BPbFexbvB6U2l5x9eXTftHhdisnSdX4VIkRM8s3njkG4U6gOSqDB1fzd1bN6Xr1Y aSkfTAyi0y8pM5L0T1UWQ45zcScf839GxQEkFsc5yqXA54xpZDvuixXqxVOLHWm9 KBiiKsyddWapBfo6BMTCWdyUbw0o

From Ole Streicher@21:1/5 to Santiago Vila on Tue Dec 27 13:40:01 2022

Hi Santiago,

Santiago Vila <[email protected]> writes:

If you don't have deb-src lines, they are the same as the usual deb lines except that they begin with deb-src.

Just curious: why are the deb line not used by default here?

Best

Ole

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Santiago Vila@21:1/5 to All on Tue Dec 27 13:50:01 2022

El 27/12/22 a las 13:12, Ole Streicher escribió:

Santiago Vila <[email protected]> writes:

If you don't have deb-src lines, they are the same as the usual deb lines
except that they begin with deb-src.

Just curious: why are the deb line not used by default here?

There is a question during install about deb-src lines (in expert mode
at least), and the user has the opportunity to say "no", so it is possible
that OP does not have those lines in his system by default.

(Not sure at all if that was the meaning of your question)

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Barry Scott@21:1/5 to Santiago Vila on Tue Dec 27 17:30:01 2022

This is a multi-part message in MIME format.
On 27/12/2022 12:49, Santiago Vila wrote:

El 27/12/22 a las 13:12, Ole Streicher escribió:

Santiago Vila <[email protected]> writes:

If you don't have deb-src lines, they are the same as the usual deb
lines
except that they begin with deb-src.

Just curious: why are the deb line not used by default here?

There is a question during install about deb-src lines (in expert mode
at least), and the user has the opportunity to say "no", so it is
possible
that OP does not have those lines in his system by default.

I do not recall Ubuntu asking such a question.

But the deb-src lines are in the /etc/apt/sources.list but commented
out.

(Not sure at all if that was the meaning of your question)

<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
 

<div class="moz-cite-prefix">On 27/12/2022 12:49, Santiago Vila
wrote: 
</div>
<blockquote type="cite"
cite="mid:[email protected]">El
27/12/22 a las 13:12, Ole Streicher escribió:
 
<blockquote type="cite">Santiago Vila <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a>
writes:
 
<blockquote type="cite">If you don't have deb-src lines, they
are the same as the usual deb lines
 
except that they begin with deb-src.
 
</blockquote>
 
Just curious: why are the deb line not used by default here?
 
</blockquote>
 
There is a question during install about deb-src lines (in expert
mode
 
at least), and the user has the opportunity to say "no", so it is
possible
 
that OP does not have those lines in his system by default.
 
</blockquote>
I do not recall Ubuntu asking such a question.
But the deb-src lines are in the /etc/apt/sources.list
but commented 
out. 

<blockquote type="cite"
cite="mid:[email protected]">
 
(Not sure at all if that was the meaning of your question)
 
 
</blockquote>
</body>
</html>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Barry Scott@21:1/5 to Ole Streicher on Tue Dec 27 17:30:01 2022

On 27/12/2022 11:16, Ole Streicher wrote:

Hi Barry,

Barry Scott <[email protected]> writes:

I am build my first Debian package for Barry's Emacs
(https:://barrys-emacs.org)

Aside from Santiagos technical tips: If you really want to contribute
your package to the Debian distribution, you should also have a few
other things in mind:

* Your package should come with a proper DFGS compliant [1] license. Your
Github upstream package [2] doesn't have one, and it would be useful
(not only for Debian packaging) to add one there.

I plan to state it is Apache-2.0 licensed. There is an issue to fix this.

* I would recommend to follow the usual procedures here. Specifically,
you should open an "Intend To Package" (ITP) bug [3] to indicate your
packaging efforts.

Happy to contribute bemacs and my other packages to debian.

The others include scm-workbench, but that needs PyQt6 Scintilla
to get packaged only PyQt5 Scintilla is packaged at the moment.
Also I need to package PyPI xml-preferences (I'm upstream for that
as well.

I guess I need an account in the debian infrastructure to do the work
under?

Bare in mind that I know nothing about what is expected in terms of
accounts, contrib agreements etc for debian.

Learning debian's ways is like learning a foreign language, there is new grammar and vocabulary I'm encountering. I know the Fedora RPM
grammar and vocabulary (I'm a Fedota packager).

* The target distribution for the packaging is "unstable" (sid). From
there it migrates to the Debian distribution. It also migrates to
Ubuntu, Mint, and all the other derivative distributions.

Cool.

* The packaging efforts should be separated from the software
development itself and usually happens on the Salsa Gitlab server
[4]. I'd strongly recommend to allow team maintainance, to lower the
barrier of packaging-related contributions.

I develop features and packaging together as they often play into each
other.

I support 4 OS (Fedora, macOS, Windows, netbsd) at the moment and want to
add debian/ubuntu.

Being able to experiment with packaging is valuable to me.

I can use the native debian workflow for releasing to public consumption.
As I do for Fedora packages I'm the maintainer for.

Barry

Best regards

Ole

[1] https://www.debian.org/social_contract#guidelines
https://wiki.debian.org/DFSGLicenses
[2] https://github.com/barry-scott/BarrysEmacs
[3] https://wiki.debian.org/ITP
[4] https://salsa.debian.org

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Soren Stoutner@21:1/5 to All on Tue Dec 27 10:57:51 2022

Copy: [email protected] (Barry Scott)

This is a multi-part message in MIME format.

--nextPart12480706.mlJVIYQJcM
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="iso-8859-1"

Barry,

Figuring out how to package for Debian has a stiff learning curve (speaking as someone
who is going through the process myself).

There are a couple of website that collect links to information that might be useful to you.

https://mentors.debian.net/intro-maintainers/[1]

https://wiki.debian.org/Packaging[2]

The references that I personally found most helpful were there following:

https://packages.debian.org/bookworm/developers-reference[3]
(Install the package and then read /usr/share/developers-reference/developers- reference.pdf)

https://packages.debian.org/bookworm/maint-guide[4]
(Install the package and then read /usr/share/doc/maint-guide/maint-guide.en.pdf)

Note that this document is considered outdated and replaced by https://www.debian.org/
doc/manuals/debmake-doc/index.en.html[5] but I found it to be a more useful read, even
though they share an author. You will discover that almost all Debian documentation is
outdated, because writing documentation is almost always less exciting than writing code.
So, you almost always have to adjust anyway.

Also, if you decide to use Git, definitely check out the git-buildpackage documentation:

https://packages.debian.org/bookworm/git-buildpackage[6]
(Install the package and then read /usr/share/doc/git-buildpackage/manual-html/ index.html)

On Tuesday, December 27, 2022 9:24:18 AM MST Barry Scott wrote:

On 27/12/2022 11:16, Ole Streicher wrote:

Hi Barry,

Barry Scott <[email protected]> writes:

I am build my first Debian package for Barry's Emacs
(https:://barrys-emacs.org)

Aside from Santiagos technical tips: If you really want to contribute
your package to the Debian distribution, you should also have a few
other things in mind:

* Your package should come with a proper DFGS compliant [1] license. Your

Github upstream package [2] doesn't have one, and it would be useful
(not only for Debian packaging) to add one there.

I plan to state it is Apache-2.0 licensed. There is an issue to fix this.

* I would recommend to follow the usual procedures here. Specifically,

you should open an "Intend To Package" (ITP) bug [3] to indicate your
packaging efforts.

Happy to contribute bemacs and my other packages to debian.

The others include scm-workbench, but that needs PyQt6 Scintilla
to get packaged only PyQt5 Scintilla is packaged at the moment.

--nextPart12480706.mlJVIYQJcM
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="iso-8859-1"

<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>Barry,
 Figuring out how to package for Debian has a stiff learning curve (speaking as someone who is going through the process myself).
 There are a couple of website that collect links to information that might be useful to you.
 <a href="https://mentors.debian.net/intro-maintainers/">https://mentors.debian.net/intro-maintainers/</a>
 <a href="https://wiki.debian.org/Packaging">https://wiki.debian.org/Packaging</a>
 The references that I personally found most helpful were there following:
 <a href="https://packages.debian.org/bookworm/developers-reference">https://packages.debian.org/bookworm/developers-reference</a>
(Install the package and then read /usr/share/developers-reference/developers-reference.pdf)
 <a href="https://packages.debian.org/bookworm/maint-guide">https://packages.debian.org/bookworm/maint-guide</a>
(Install the package and then read /usr/share/doc/maint-guide/maint-guide.en.pdf)
 Note that this document is considered outdated and replaced by <a href="https://www.debian.org/doc/manuals/debmake-doc/index.en.html">https://www.debian.org/doc/manuals/debmake-
doc/index.en.html</a> but I found it to be a more useful read, even though they share an author.  You will discover that almost all Debian documentation is outdated, because writing documentation is almost always less exciting than writing code.
  So, you almost always have to adjust anyway.
 Also, if you decide to use Git, definitely check out the git-buildpackage documentation:
 <a href="https://packages.debian.org/bookworm/git-buildpackage">https://packages.debian.org/bookworm/git-buildpackage</a>
(Install the package and then read /usr/share/doc/git-buildpackage/manual-html/index.html)
 On Tuesday, December 27, 2022 9:24:18 AM MST Barry Scott wrote:
> On 27/12/2022 11:16, Ole Streicher wrote:
> > Hi Barry,
> > 
> > Barry Scott <[email protected]> writes:
> >> I am build my first Debian package for Barry's Emacs
> >> (https:://barrys-emacs.org)
> > 
> > Aside from Santiagos technical tips: If you really want to contribute
> > your package to the Debian distribution, you should also have a few
> > other things in mind:
> > 
> > * Your package should come with a proper DFGS compliant [1] license. Your
> > 
> >    Github upstream package [2] doesn't have one, and it would be useful
> >    (not only for Debian packaging) to add one there.
> > I plan to state it is Apache-2.0 licensed. There is an issue to fix this.
> > > * I would recommend to follow the usual procedures here. Specifically,
> > 
> >    you should open an "Intend To Package" (ITP) bug [3] to indicate your
> >    packaging efforts.
> > Happy to contribute bemacs and my other packages to debian.
> > The others include scm-workbench, but that needs PyQt6 Scintilla
> to get packaged only PyQt5 Scintilla is packaged at the moment.
> Also I need to package PyPI xml-preferences (I'm upstream for that
> as well.
> > I guess I need an account in the debian infrastructure to do the work
> under?
> > Bare in mind that I know nothing about what is expected in terms of
> accounts, contrib agreements etc for debian.
> > Learning debian's ways is like learning a foreign language, there is new
> grammar and vocabulary� I'm encountering. I know the Fedora RPM
> grammar and vocabulary� (I'm a Fedota packager).
> > > * The target distribution for the packaging is "unstable" (sid). From
> > 
> >    there it migrates to the Debian distribution. It also migrates to
> >    Ubuntu, Mint, and all the other derivative distributions.
> > Cool.
> > > * The  packaging   efforts  should   be  separated  from   the  software
> > 
> >    development  itself and  usually happens  on the  Salsa Gitlab  server
> >    [4]. I'd strongly  recommend to allow team maintainance,  to lower the
> >    barrier of packaging-related contributions.
> > I develop features and packaging together as they often play into each
> other.
> > I support 4 OS (Fedora, macOS, Windows, netbsd) at the moment and want to
> add debian/ubuntu.
> > Being able to experiment with packaging is valuable to me.
> > I can use the native debian workflow for releasing to public consumption.
> As I do for Fedora packages I'm the maintainer for.
> > Barry
> > > Best regards
> > 
> > Ole
> > 
> > 
> > [1] https://www.debian.org/social_contract#guidelines
> > 
> >      https://wiki.debian.org/DFSGLicenses
> > 
> > [2] https://github.com/barry-scott/BarrysEmacs
> > [3] https://wiki.debian.org/ITP
> > [4] https://salsa.debian.org
 -- 
Soren Stoutner
[email protected]
</body>
</html>
--nextPart12480706.mlJVIYQJcM--

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAmOrMh8ACgkQwufLJ66w tgPmdRAAjI3RHa/WmTrESzQnjG4l3WkiPhyZnoAL+3v4OlnZ0kAGbRHMLalLhP3T 2Hsc257MlHvuAyU9DyqjeDaG7fEUi4Y6syhlta7TdzK3mLJgGpNYJZaJxN7DcjdW eJ3qaNA93ZBqPLGoLa3xhFI0qATpu/lg9i76DoLQ53ApVQdOXiiDgR7qf+s5lVQ0 Cx7O/eq5tlErS82L0wTaA9IHEwSo+0RyNA4mH7ZIPlKJPVGg/bEsqF+elPzkIXKh ZfOy6j61Zs1z7KsQxeC7hmSI6kt7+fkLVDlhNJchSuidjFM2wy2/ATdLjfqho7Ea ZtFmx6rTyH7DG+RIticp55m9E7M9LrWSNWRDI4EqanxsUtoskjRx7Gme608kUDOz VHnemeG5TbnG9+RbdUzGWM7Vc5lwnvWO7ZBo9SAuK0Lr/dKVy40OHldFTLY2Vcr1 xdNZH5IaKi+2oxZUaP992RSUb+n0waI/P0ltoy9u2kBK+bG1c4TPy4BKJ+orIoig Rn9ganapeCPFXWrAgsV4LZA0ZCKehYg2zI6q550U+VtGokqcO7QQYMiCO4ug6I/5 DPYpJCYYlrnp0wNuQBOd73af4P5h3QDN3yqRpWJ3tOu6i1IWKVqb4u3kG6lS+4JD H71kLrNV20vLcan0iEaFe7S1EcZoviNI8g+2DfaBmhL2md6wQ70=
=QPdS
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Andrew M.A. Cater@21:1/5 to Soren Stoutner on Tue Dec 27 20:10:02 2022

On Tue, Dec 27, 2022 at 10:57:51AM -0700, Soren Stoutner wrote:

Barry,

Figuring out how to package for Debian has a stiff learning curve (speaking as someone
who is going through the process myself).

There are a couple of website that collect links to information that might be useful to you.

I'd also add Raphael Hertzog's Debian handbook for most things Debian

debian-handbook is the Debian package to install, though you can
also buy a printed version. It's a gold mine of generally useful
information structured as a case study of an imaginary factory setup but
with good information on specfics.

All best,

Andy Cater

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Barry Scott@21:1/5 to Andrew M.A. Cater on Wed Dec 28 22:50:02 2022

On 27/12/2022 19:06, Andrew M.A. Cater wrote:

On Tue, Dec 27, 2022 at 10:57:51AM -0700, Soren Stoutner wrote:

Barry,

Figuring out how to package for Debian has a stiff learning curve (speaking as someone
who is going through the process myself).

I have given up a number of times in the past - but having this mentor
list is most valuable!

I think the docs are better then a few years ago when I last tried to
create a .deb.

There are a couple of website that collect links to information that might be useful to you.

I'd also add Raphael Hertzog's Debian handbook for most things Debian

debian-handbook is the Debian package to install, though you can
also buy a printed version. It's a gold mine of generally useful
information structured as a case study of an imaginary factory setup but
with good information on specfics.

Soren, Andrew,

Thanks for the reading materials!

If you ever need to package RPMs I can return the favor.

Barry

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Soren Stoutner@21:1/5 to All on Thu Dec 29 09:42:00 2022

Copy: [email protected] (Barry Scott)

This is a multi-part message in MIME format.

--nextPart3734763.RnS4kX4XeW
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"

On Wednesday, December 28, 2022 2:49:19 PM MST Barry Scott wrote:

If you ever need to package RPMs I can return the favor.

I might some day. I am the upstream developer for Privacy Browser PC, which will
shortly reach an alpha release. I am planning to maintain Debian packages, but I
might also want to maintain official RPMs.

https://www.stoutner.com/privacy-browser-pc/[1]

--
Soren Stoutner
[email protected]

--------
[1] https://www.stoutner.com/privacy-browser-pc/

--nextPart3734763.RnS4kX4XeW
Content-Transfer-Encoding: 7Bit
Content-Type: text/html; charset="us-ascii"

<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>On Wednesday, December 28, 2022 2:49:19 PM MST Barry Scott wrote:
> If you ever need to package RPMs I can return the favor.
 I might some day.  I am the upstream developer for Privacy Browser PC, which will shortly reach an alpha release.  I am planning to maintain Debian packages, but I
might also want to maintain official RPMs.
 <a href="https://www.stoutner.com/privacy-browser-pc/">https://www.stoutner.com/privacy-browser-pc/</a>
 -- 
Soren Stoutner
[email protected]
</body>
</html>
--nextPart3734763.RnS4kX4XeW--

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAmOtw1gACgkQwufLJ66w tgO+dw/8D+boNiJ1m7c20o5Nig6MQ2REIt0cZZYG9tmloGLWn9cT/XosUIGkxwcv RI2QO8Hx1OE0ANR4qthhrgzYrjujMKoCRfw/lkuidUH2z8VoOJeE9dxhkoHkOjPG bEUZMsbyLWfChUcM8NfYVHsHJ1IQ/tF1r1T7BNNrKPWSfW3+EZWjByysV8UxV8g4 5aolwjWOpSPvwtxlfuAJVFJeSoR9MbgJJUBlxzH7W2f2P7h1ffHZCqbDyALNXQRa oE7BPhikN9aYmOL4pNlj0uPQj/bovH7vii26BdTFlkdhZhggnbnaGY9bavEA+ILZ TpwK3AhocQkDgMePFY881npPG7jg7mTnKpIF3gM5MFq391cBtEnlswGUlZ7wS1nY tIsxZL71oAA5ovJn5Wjg6cCoX7anq0GpxAfZiB/McgxVsg7R70DFy5uHSO39+BYg wr9MGwXBj1aiqlmP3lYn0L7LBiFJHVWkVYJOV5O9RsKrsEd8YgK3Q81BgiOmgeAx Hm0aabBBnS9dH2vwVyvLPJvZTwNjaZxzujHYWn5MuWcdN8bCLfu9o39yhotd7cTa GYgoZdbZEkUBufhlTBe3gnXY5sGQYMsRv3h9l5EQYjTBs3Dkr5++h/ntFv5d8P4J N8xAZNqZhkPv+BzDhXJTANH+5Wa+U4F13o36dZ+xfhvu3iFhLXw=
=cx83
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Who's Online
Recent Visitors
- Krenn
  Sat Jun 6 11:38:56 2026
  from Sydney, Nsw via Telnet
- Furryboy
  Sat Jun 6 10:56:29 2026
  from Romania, Galati via SSH
- Centurion
  Fri Jun 5 22:28:01 2026
  from Berea, Ohio via Telnet
- Ab Cadd
  Fri Jun 5 17:52:51 2026
  from Sheboygan, Wi via Telnet
- Gwylbert
  Fri Jun 5 06:28:52 2026
  from Sydney, Nsw via Telnet
- Centurion
  Thu Jun 4 23:42:23 2026
  from Berea, Ohio via Telnet
- Michal Wronka
  Thu Jun 4 23:19:58 2026
  from Wroclaw, Poland via Telnet
- Michal Wronka
  Thu Jun 4 23:17:20 2026
  from Wroclaw, Poland via SSH

System Info

Sysop:	Keyop
Location:	Huddersfield, West Yorkshire, UK
Users:	715
Nodes:	16 (2 / 14)
Uptime:	144:11:41
Calls:	12,089
Calls today:	2
Files:	15,000
Messages:	6,517,483

lintian errors packaging Barry's Emacs

Who's Online

Recent Visitors

System Info