Forum: Too Lazy BBS

Who's Online
Recent Visitors
- Guest
  Tue Feb 4 01:00:14 2025
  from Nashville, Tn via Telnet
- Codefenix
  Thu Jan 30 18:53:44 2025
  from Canton, Oh via Telnet
- Rixter
  Thu Jan 30 08:47:04 2025
  from Madison, Nc via SSH
- Stern
  Sat Jan 25 20:33:42 2025
  from Davis, California via SSH

System Info

Sysop:	Amessyroom
Location:	Fayetteville, NC
Users:	43
Nodes:	6 (0 / 6)
Uptime:	94:25:16
Calls:	290
Calls today:	1
Files:	904
Messages:	76,378

Re: Bug#1074498: RFS: baby/1.0.55-1 [ITP] -- Abbreviate long commands i

From Soren Stoutner@21:1/5 to Manuel Guerra on Mon Jul 29 22:27:32 2024

Copy: debian-mentors@lists.debian.org (Debian Mentors)

This is a multi-part message in MIME format.

--nextPart3920063.vKdlhCYIIj
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="UTF-8"

Manuel,

Everything looks good to me. I submitted the package. Because it is a new package, it will
go through the NEW queue to be manually reviewed by one of the FTP Masters. If we have
done our work well it should be accepted without comment.

You will receive an email shortly notifying you it has been processed into the NEW queue.
You can follow the NEW queue status at:

https://ftp-master.debian.org/new.html

Once your package has been approved, you will be able to see an overview of the health of
the package in Debian at:

https://tracker.debian.org/pkg/baby

(currently this URL is not valid)

In the future, when you have updates, just shoot me an email and I can sponsor them.
Also, I would recommend you consider becoming a Debian Maintainer (DM). It is a bit of
work, and you probably want to become involved with several different packages, but it is
rewarding. DMs can be granted upload rights to specific packages they have a track record
of handling with expertise. So, as a DM you could be granted permissions to update baby
and other packages your work on without the need of having to get a DD to sponsor them.

https://wiki.debian.org/DebianMaintainer[1]

Soren

On Monday, July 29, 2024 10:05:24 PM MST Manuel Guerra wrote:

Soren

Sorry, I was very confused!

I will implement this: 3. Handle the Debian packaging on Salsa.

The package has a new upload 1.0.58 with all the changes aplied, please
when you have a free time take a look on it.

Regards,
Manuel

El lun, 29 de jul. de 2024 19:54, Soren Stoutner <soren@debian.org>

escribió:

Manuel,

On Monday, July 29, 2024 3:18:33 PM MST Manuel Guerra wrote:

Soren

I see in your output version 1.0.55, actual version is 1.0.57, please use the repository at https://github.com/manuwarfare/baby.git

By this way I actually build good using sbuild

I (re)moved the package files from Salsa to Github :-(

I’m curious as to why you decided to do this (see more discussion below).

Please advise me if the issues was solved. Thanks!

--nextPart3920063.vKdlhCYIIj
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="UTF-8"

<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>Manuel,
 Everything looks good to me.  I submitted the package.  Because it is a new package, it will go through the NEW queue to be manually reviewed by one of the FTP Masters.&
nbsp; If we have done our work well it should be accepted without comment. You will receive an email shortly notifying you it has been processed into the NEW queue.  You can follow the NEW queue status at:
 https://ftp-master.debian.org/new.html
 Once your package has been approved, you will be able to see an overview of the health of the package in Debian at:
 https://tracker.debian.org/pkg/baby
 (currently this URL is not valid)
 In the future, when you have updates, just shoot me an email and I can sponsor them.  Also, I would recommend you consider becoming a Debian Maintainer (DM).  It is a
bit of work, and you probably want to become involved with several different packages, but it is rewarding.  DMs can be granted upload rights to specific packages they have a track record of handling with expertise.  So, as a DM you could be
granted permissions to update baby and other packages your work on without the need of having to get a DD to sponsor them.
 <a href="https://wiki.debian.org/DebianMaintainer">https://wiki.debian.org/DebianMaintainer</a>
 Soren
 On Monday, July 29, 2024 10:05:24 PM MST Manuel Guerra wrote:
> Soren
> > Sorry, I was very confused!
> > I will implement this: 3.  Handle the Debian packaging on Salsa.
> > The package has a new upload 1.0.58 with all the changes aplied, please
> when you have a free time take a look on it.
> > Regards,
> Manuel
> > El lun, 29 de jul. de 2024 19:54, Soren Stoutner <soren@debian.org>
> > escribió:
> > Manuel,
> > 
> > On Monday, July 29, 2024 3:18:33 PM MST Manuel Guerra wrote:
> > > Soren
> > > 
> > > I see in your output version 1.0.55, actual version is 1.0.57, please use
> > > the repository at https://github.com/manuwarfare/baby.git
> > > 
> > > By this way I actually build good using sbuild
> > > 
> > > I (re)moved the package files from Salsa to Github :-(
> > 
> > I’m curious as to why you decided to do this (see more discussion below).
> > 
> > > Please advise me if the issues was solved. Thanks!
> > 
> > This did resolve the build problem.  However, it introduced a new problem.
> > 
> > W: baby source: no-debian-changes
> > N:
> > N:   This non-native package makes no changes to the upstream sources in
> > the
> > N:   Debian-related files.
> > N:
> > N:   Maybe a mistake was made when the upstream tarball was created, or
> > maybe
> > N:   this package is really a native package but was built non-native by
> > N:   mistake.
> > N:
> > N:   Debian packaging is sometimes maintained as part of upstream, but
> > that is
> > N:   not recommended as best practice. Please make this package native, if
> > the
> > N:   software is only for Debian. Otherwise, please remove the debian
> > directory
> > N:   from upstream releases and add it in the Debian packaging.
> > N:
> > N:   Format 1.0 packages are subject to the restriction that the diff
> > cannot
> > N:   remove files from the debian directory. For Format 3.0 packages, the
> > N:   debian directory is automatically purged during unpacking.
> > N:
> > N:   Visibility: warning
> > N:   Show-Always: no
> > N:   Check: files/artifact
> > N:   Renamed from: empty-debian-diff
> > 
> > Basically, a non-native package like yours should not contain a debian
> > directory in the orig.tar.gz.  That directory should only exist in the
> > debian.tar.xz.  That means that uscan needs to point to a repository or a
> > tarball that doesn’t contain a debian directory.
> > 
> > There are several ways you can do this (the following is probably not an
> > exhaustive list).
> > 
> > 1.  Use a separate branch in your upstream repository for the Debian
> > packaging.
> > 
> > 2.  Use a separate repository on github for the Debian packaging.
> > 
> > 3.  Handle the Debian packaging on Salsa.
> > 
> > For the purposes of sponsoring your package, it doesn’t matter to me which
> > of
> > these solutions you choose.  For me personally, where I am both upstream
> > and
> > the package maintainer, I have gone with option 3.
> > 
> > https://gitweb.stoutner.com/?p=PrivacyBrowserPC.git;a=tree
> > 
> > https://salsa.debian.org/soren/privacybrowser
> > 
> > However, it is fine if you decide not to use Salsa for any reasons that
> > are
> > important to you.
> > 
> > Soren
> > 
> > --
> > Soren Stoutner
> > soren@debian.org
 -- 
Soren Stoutner
soren@debian.org
</body>
</html>
--nextPart3920063.vKdlhCYIIj--

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

iQIzBAABCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAmaoecQACgkQwufLJ66w tgOXThAAnYyAuKKwOZmgMGsflPOzxlM6gsRLA8p7jfwWCTsbK3m2pE9sIEB9dCcd 4BmvgpN6emelrV6g/phkKEnKmLK2MMimAytFTcT2etB5l4S/JtaXx0fwhz4YJR9u KZAYmxUG4VngCcclIojzXoQl7qnr/JaExWxVtCYdk9UDExFxScR6pccDxtSqsxv8 1YN+eA0xUG55JXkdoZF29y1AslhZm6afGXACLnILTNM5XnaJGX2PJhpOSgK9qS80 gV/hAmP3XAHGQbHIRi6w6b8T0lI4B50aqGeq6xFookyRlASQAeJZ4GOI03wWDsqT S+Hf2lr9VWxoNdJPRQvSvCjxcxAAtd0ObICB60N+Dhr7GHh/OzBRmXF0hjchbXZd 52RpL9xbxJ6s3pbEuiB1fy3mDkZtu8yQ+Kulc4hesK490Q/oPcNV/pIj5yaB4lJd PYsqtFsXx3vc42O9qLCBbNxlalvp+PWK9LOAPUrw3oRPlRMYowz58mkZ0WcubSW2 w7Kucs1Dn2cQFakbH/RKF9FZvoHhk6Njul0hVAIqaYD6wWxTEBD4mbnjX2lEaoTv cLi/Jq/jtzRszx9j5c7RjSR77Fxplod9EzEufAp8eg33H+YO5/URf1mqklNhcJX+ NcN9EzV5o5PhVWlryZxInlNDMEQ+DlcNQ4sTsQgyk3KXdBDbk8Q=
=cIVg
-----END PGP SIGNATURE-----

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

From Phil Wyett@21:1/5 to Soren Stoutner on Tue Jul 30 12:30:01 2024

Hi Manuel,

Congratulations on creating baby and preparing it to be now in the NEW queue and ready to enter Debian. Your skill, perseverance and attitude do you great credit.

Hope to work with you in and around Debian in the future.

Regards

Phil

On Mon, 2024-07-29 at 22:27 -0700, Soren Stoutner wrote:

Manuel,

Everything looks good to me. I submitted the package. Because it is a new package, it will go through the NEW queue to be manually reviewed by one of the FTP Masters. If we have done our work well it should be accepted without comment.

You will receive an email shortly notifying you it has been processed into the NEW queue. You can follow the NEW queue status at:

https://ftp-master.debian.org/new.html

Once your package has been approved, you will be able to see an overview of the health of the package in Debian at:

https://tracker.debian.org/pkg/baby

(currently this URL is not valid)

In the future, when you have updates, just shoot me an email and I can sponsor them. Also, I would recommend you consider becoming a Debian Maintainer (DM). It is a bit of work, and you probably want to become involved with several different packages, but it is rewarding. DMs can be granted upload rights to specific packages they have a track record of handling with expertise. So, as a DM you could be granted permissions to update baby and other packages your work on without the need of having to
get a DD to sponsor them.

https://wiki.debian.org/DebianMaintainer

Soren

On Monday, July 29, 2024 10:05:24 PM MST Manuel Guerra wrote:

Soren

Sorry, I was very confused!

I will implement this: 3. Handle the Debian packaging on Salsa.

The package has a new upload 1.0.58 with all the changes aplied, please when you have a free time take a look on it.

Regards,
Manuel

El lun, 29 de jul. de 2024 19:54, Soren Stoutner <soren@debian.org>

escribió:

Manuel,

On Monday, July 29, 2024 3:18:33 PM MST Manuel Guerra wrote:

Soren

I see in your output version 1.0.55, actual version is 1.0.57, please use
the repository at https://github.com/manuwarfare/baby.git

By this way I actually build good using sbuild

I (re)moved the package files from Salsa to Github :-(

I’m curious as to why you decided to do this (see more discussion below).

Please advise me if the issues was solved. Thanks!

This did resolve the build problem. However, it introduced a new problem.

W: baby source: no-debian-changes
N:
N: This non-native package makes no changes to the upstream sources in
the
N: Debian-related files.
N:
N: Maybe a mistake was made when the upstream tarball was created, or maybe
N: this package is really a native package but was built non-native by
N: mistake.
N:
N: Debian packaging is sometimes maintained as part of upstream, but that is
N: not recommended as best practice. Please make this package native, if
the
N: software is only for Debian. Otherwise, please remove the debian directory
N: from upstream releases and add it in the Debian packaging.
N:
N: Format 1.0 packages are subject to the restriction that the diff cannot
N: remove files from the debian directory. For Format 3.0 packages, the
N: debian directory is automatically purged during unpacking.
N:
N: Visibility: warning
N: Show-Always: no
N: Check: files/artifact
N: Renamed from: empty-debian-diff

Basically, a non-native package like yours should not contain a debian directory in the orig.tar.gz. That directory should only exist in the debian.tar.xz. That means that uscan needs to point to a repository or a
tarball that doesn’t contain a debian directory.

There are several ways you can do this (the following is probably not
an
exhaustive list).

1. Use a separate branch in your upstream repository for the Debian packaging.

2. Use a separate repository on github for the Debian packaging.

3. Handle the Debian packaging on Salsa.

For the purposes of sponsoring your package, it doesn’t matter to me which
of
these solutions you choose. For me personally, where I am both
upstream
and
the package maintainer, I have gone with option 3.

https://gitweb.stoutner.com/?p=PrivacyBrowserPC.git;a=tree

https://salsa.debian.org/soren/privacybrowser

However, it is fine if you decide not to use Salsa for any reasons that are
important to you.

Soren

--
Soren Stoutner
soren@debian.org

--
Soren Stoutner
soren@debian.org

--

"I play the game for the game’s own sake"

Arthur Conan Doyle - The Adventure of the Bruce-Partington Plans

--

Internet Relay Chat (IRC): kathenas

Website: https://kathenas.org

Instagram: https://instagram.com/kathenasorg/

Buy Me A Coffee: https://buymeacoffee.com/kathenasorg

--

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

iQJOBAABCAA4FiEEcKCsRax3nv6E9jrtckqptS8CTIsFAmaovjAaHHBoaWxpcC53 eWV0dEBrYXRoZW5hcy5vcmcACgkQckqptS8CTItxWA//WrNFyPNXqx/SAXr9eCcR c+POnpthafUMW0a+cVeeBjr99l/utbJn9+CHgXZxlpgKJnCSmI3o2wtKoofx14ys Ah0BXKwGDoUxwdTjjT35zlbXgGqSUmMjX4b5tRBKYeyqzhx8x21WgoKVYgEn8mea Wywi+wD7lgnVTlp8+kSDN7Wo+Kqzdyl7xM/3l4IoZ1UIXD6C1h7GWW+MKKcj4cKw FoXhE22JwSqtvxEizkJhNeWanDDu2z5LgO3NA8GT1NUg9TS88IhJnaQI9SEG8g85 5sjKUhmNajHqq8R+2LLxZfd2gd/NVooFhV7nRrt55QBXkbObUQ5ktG5lBQ9tXEd2 iGHuYSnN33tWjIXK27fANG6Jc3imNah57WfRQ7C8lHQhojXVJwd+Y+Nu3FxvpN6r AGFXoo9lad6QZHiI2OOsBbi98HH+BVneN9fwmUMAR9Uc2oKlj1BRJiCFWnfr3W9H LaXfuhgdPSAe5XjsBtiWAN8xF+W4wv0/GaI6OwXsDr/c0s1haDVAMT6jUZU0/k7/
Rj2u8tM7z90Q+

Who's Online

Recent Visitors

System Info

Re: Bug#1074498: RFS: baby/1.0.55-1 [ITP] -- Abbreviate long commands i