Your message dated Sun, 27 Sep 2020 09:04:12 +0000
with message-id <e1kmsbm-0007mh...@fasolo.debian.org>
and subject line Bug#961371: fixed in due 2.0.0-3
has caused the Debian Bug report #961371,
regarding ITP: due -- Wrapper tool to create and run Docker container software 
build environments.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
961371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961371
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: adoyle <alexddo...@gmail.com>

* Package name    : due
  Version         : 1.3.1
  Upstream Author : Alex Doyle <alexddo...@gmail.com>
* URL             : https://github.com/CumulusNetworks/DUE
* License         : MIT
  Programming Lang: Bash
  Description     : Wrapper tool to create and run Docker container software 
build environments.

Dedicated User Environment (DUE) is a framework for creating preconfigured 
build/development
environments in Docker containers. It serves two primary purposes:

1 - Maintains configurations for creating Docker images for any build 
environment, using
any architecture of any Debian based release it can find an image for.
 For example, the Open Network Install Environment 
(https://github.com/opencomputeproject/onie)
 currently builds on Debian 8 and 9, but requires some Backports packages, and 
a program that
 isn't packaged for Debian. DUE maintains a configuration to get all of that 
added when the
 Docker image is created so ONIE can 'just build'. Apart from not requiring the 
end user to
 have to configure the build environment, it also allows all developers to use 
the same build
 environment when debugging - regardless of where they happen to be.

2 - It goes beyond 'just using a Dockerfile' by using a launcher application 
that supplies
runtime configuration to Docker for the Docker images it has created. Apart 
from reducing
typing and being smart about the containers that it runs (ex: containers 
building Debian
packages mount the host directory _above_ the build directory so the resulting 
.debs aren't
stored in the container), DUE preserves the user's identity in the container by 
creating an account
for them with their user ID, and mounting their home directory so they can 
access their .config files.
This creates a less intrusive development environment when the user is in a 
build/test/debug
cycle.

While the above are the most important features DUE provides, there are a lot 
more ways
it makes using different development configurations easier, which are 
documented in
the Readme.md (https://github.com/CumulusNetworks/DUE/blob/master/README.md)

I also created a tutorial video using DUE to build ONIE as part of a talk I 
gave at
OpenCompute here: https://www.youtube.com/watch?v=-5onRbZA0QQ&feature=youtu.be

History:
 DUE came out of work I did at Cumulus Networks to provide build environments 
for
 teams of engineers building packages for Cumulus' Jessie and Buster based
 releases of Cumulus Linux. When I took over as ONIE Project Lead, I saw the 
opportunity
 to use it to create a standard way of setting up build environments for ONIE 
and any other
 software projects. Cumulus saw the value in any developer being able to use it
 and DUE was open sourced under the MIT license.

Q&A:
Why is this package useful/relevant?
 See above.

Is it a dependency for another package?
 No. It does require a version ( Debian or upstream ) of Docker to work though.

Do you use it?
 All. The. Time.  Building packages at work, building ONIE, and if I just need
 an environment to quickly test configuration changes.
 This 'dogfooding' has provided insight into fixing program behaviors that
 initially seemed okay, and then became irritating through repeated use.

If there are other packages providing similar functionality, how does it 
compare?
 I looked around for quite a while before starting on DUE ( why reinvent the 
wheel?),
 but couldn't find anything that had the combination of:
  - Consistent, user friendly interface
  - Easy build environment configuration
  - And support for Debian derivatives
  ...that I was looking for.
 
 I think the closest software to this would be using schroots, and while they
 can be functionally the same, the end user experience, especially for users 
that
 are new to Debian ( or are trying to build code that partially exists outside
 the Debian ecosystem ) has less of a learning curve, and is faster to set up.
 
How do you plan to maintain it?
 I will be updating the upstream source and doing the work to make sure it is
 Debian compliant.
 
Are you looking for co-maintainers?
 Not at the moment.
 
Do you need a sponsor?
 Yes, as I am not a Debian Developer ( in the official sense, anyway :) )
 
Thank you for your consideration,
Alex Doyle

--- End Message ---
--- Begin Message ---
Source: due
Source-Version: 2.0.0-3
Done: Geert Stappers <stapp...@debian.org>

We believe that the bug you reported is fixed in the latest version of
due, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 961...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Geert Stappers <stapp...@debian.org> (supplier of updated due package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sun, 27 Sep 2020 10:45:53 +0200
Source: due
Architecture: source
Version: 2.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Alex Doyle <alexddo...@gmail.com>
Changed-By: Geert Stappers <stapp...@debian.org>
Closes: 961371
Changes:
 due (2.0.0-3) unstable; urgency=medium
 .
   * Three times should be a charm, closes: #961371.
Checksums-Sha1:
 3bca597d9161ae1af965664e598cf6f6d10045e6 1860 due_2.0.0-3.dsc
 1db7d13f9d39e6dae324947b0c0768d0818d07e8 3212 due_2.0.0-3.debian.tar.xz
 ba76edaf235c0d124d83ba365185986fadd27f96 6204 due_2.0.0-3_source.buildinfo
Checksums-Sha256:
 c99f8e7a4f85b93f561709597e0136b6a4cf53cd62bc0bdf81f0db9f78e702b5 1860 
due_2.0.0-3.dsc
 9a5af0d5cd0612546ff7d55f52c5c255f1bdd44d8de53980f780b5c8a38f78db 3212 
due_2.0.0-3.debian.tar.xz
 289f5a9238decf520fa883c3ef859f31b279c85225a165a04a29094d1bbfe26a 6204 
due_2.0.0-3_source.buildinfo
Files:
 a2f6acd4ef43a5593c729a3d00de42b5 1860 devel optional due_2.0.0-3.dsc
 ec445cf7f1174e021a352eee760d1651 3212 devel optional due_2.0.0-3.debian.tar.xz
 c7d674ef58bb2ae10886913851911387 6204 devel optional 
due_2.0.0-3_source.buildinfo

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

iQIzBAEBCAAdFiEEin8gjG2ecykWV0FNITXRI9jBm+wFAl9wUeUACgkQITXRI9jB
m+zrnQ//Vy1CWCQz+fnAIp2kGVSTvlkI8UWcWO0yNIxzhjyRtbuT9mW4z8Q+x8dx
PWeJD/CvN8TnU8cw1q7fehq9Hb4ePOXX8lBl1xCC5/mbVcibNP/YhboGBvLJyvA6
P/ZvidmKI7usHtHYWCOFfjLDgX9xHnm3eh+oPvRcCJw9ijsB+E5DbDAeIPRBZrT7
KqsqFRGoxgcqKJ5UsTmMf4gm2/JAhKr+ojQWj7WF4Ac5FWAAUCn6Rtl+gXyPh5l0
6Ew78OxdXGHJXdR6DJC0QEVKkm1X3ePXSOXxIzf/UeZkKKK4cAIfYYyzoWjKNKKz
zGazjDcyrE639KMW906vd2Aj8QHZ4JgABqCjDJ3Va4DuHlTkogaS0kKDGAh6JrJ5
4KNaeABkBShsgE2cVrBVD+HFgFJipH4RnC721KXSP/L6QMl7kSWpscSGcU4odI1P
VH3qWWKlOuwak8Q1cKx6yQ06d6Zways1WzRiVYW5j6V6psCrDg+K07/Yvra3iEac
UVh/+6cOANmYGmrj5gHdx2laSIY8JK0KFFkROJNFBbmwpBc6gontP2sHpj1hOiIg
DRAr+ns+z1z9e8XbRwO64t6wreBkTM6xSuInTE3O7XIIaHGhzKHS6ryZDu64qjGk
cpre4/dMEKrfL7aHokxSMywUUeMk5w4G4hKFdrvV27N75QYHAes=
=074v
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to