• Easier package building program

    From Osamu Aoki@21:1/5 to nerdymutualist on Sun Apr 18 04:10:01 2021
    HI,

    Actually problem is not tools but documentation of recommended
    procedure.  We need public encouragement to use current sbuild tool
    chain.  (I didn't know it has evolved so much in last ? years.)

    (Yes, I bare some responsibility...)

    On Sat, 2021-04-17 at 23:45 +0000, nerdymutualist wrote:
    Hello Debian developers and maintainers,

    When I started to venture into building my own .deb packages, I
    discovered that the process is (at least in my opinion) relatively
    complex and arduous, and a variety of tools, sometimes overlapping,
    exist to facilitate the process. On the other hand, Solus (another distribution with which I have been involved in terms of packaging)
    has a highly streamlined packaging process where most steps are
    automated and the only input required is the URL of the source
    tarball, the name of the package, and the steps to install the
    program, and a tool called solbuild (https://github.com/solus-project/solbuild) then uses OverlayFS to
    make a container, download the tarball, run the installation steps,
    detect which files were created by the installation script of the
    software, and then build the package, all automatically without
    requiring any sort of manual intervention. So I was thinking that
    perhaps this approach might be applied to Debian to streamline the
    packaging process and make it easier for people to contribute and
    maintain packages. Do you think this would be a good idea? If so, I
    would love to work on it (I am familiar with Go, Rust and Python).

    Thank you,
    Jeremy (jwinnie)


    Migrating from old pbuilder/cowbuilder practice to the current sbuild
    is what we need to promote.

    See: https://wiki.debian.org/sbuild  (I updated this recently for
    source only upload compatible shape)

    sbuild default setting uses   OverlayFS.

    Osamu




    <html><head></head><body><div>HI,</div><div><br></div><div>Actually problem is not tools but documentation of recommended procedure. &nbsp;We need public encouragement to use current sbuild tool chain. &nbsp;(I didn't know it has evolved so much in last ?
    years.)</div><div><br></div><div>(Yes, I bare some responsibility...)</div><div><br></div><div>On Sat, 2021-04-17 at 23:45 +0000, nerdymutualist wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"
    <div>Hello Debian developers and maintainers,<br></div><div><br></div><div>When I started to venture into building my own .deb packages, I discovered that the process is (at least in my opinion) relatively complex and arduous, and a variety of tools,
    sometimes overlapping, exist to facilitate the process. On the other hand, Solus (another distribution with which I have been involved in terms of packaging) has a highly streamlined packaging process where most steps are automated and the only input
    required is the URL of the source tarball, the name of the package, and the steps to install the program, and a tool called solbuild (<a href="https://github.com/solus-project/solbuild">https://github.com/solus-project/solbuild</a>) then uses OverlayFS
    to make a container, download the tarball, run the installation steps, detect which files were created by the installation script of the software, and then build the package, all automatically without requiring any sort of manual intervention. So I was
    thinking that perhaps this approach might be applied to Debian to streamline the packaging process and make it easier for people to contribute and maintain packages. Do you think this would be a good idea? If so, I would love to work on it (I am familiar
    with Go, Rust and Python).<br></div><div><br></div><div>Thank you,<br></div><div>Jeremy (jwinnie)<br></div><div><br></div></blockquote><div><br></div><div>Migrating from old pbuilder/cowbuilder practice to the current sbuild is what we need to promote.</
    <div><br></div><div>See:&nbsp;<a href="https://wiki.debian.org/sbuild">https://wiki.debian.org/sbuild</a>&nbsp; (I updated this recently for source only upload compatible shape)</div><div><br></div><div>sbuild default setting uses &nbsp; OverlayFS.</
    <div><br></div><div>Osamu</div><div><br></div><div><br></div><div><br></div><div><span></span></div></body></html>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mechtilde@21:1/5 to All on Sun Apr 18 08:00:01 2021
    This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --il4vOcL3NWEVCXrzMcAHy45Z3jFI0D9Qq
    Content-Type: text/plain; charset=utf-8
    Content-Language: en-US
    Content-Transfer-Encoding: quoted-printable

    Hello Jeremy,

    I already try to do so.

    I'm writing a shell script to automate the build process as far as possible.

    And I'm documenting it literally.

    I do it in German and it is prepared for translation.

    Source: https://salsa.debian.org/ddp-team/dpb

    Book: https://people.debian.org/~mechtilde/Dokumentation

    Cooperation is welcome.

    Regards

    Mechtilde


    Am 18.04.21 um 01:45 schrieb nerdymutualist:
    Hello Debian developers and maintainers,

    When I started to venture into building my own .deb packages, I discovered that the process is (at least in my opinion) relatively complex and arduous, and a variety of tools, sometimes overlapping, exist to facilitate the process. On the other hand,
    Solus (another distribution with which I have been involved in terms of packaging) has a highly streamlined packaging process where most steps are automated and the only input required is the URL of the source tarball, the name of the package, and the
    steps to install the program, and a tool called solbuild (https://github.com/solus-project/solbuild) then uses OverlayFS to make a container, download the tarball, run the installation steps, detect which files were created by the installation script of
    the software, and then build the package, all automatically without requiring any sort of manual intervention. So I was thinking that perhaps this approach might be applied to Debian to streamline the packaging process and make it easier for people to
    contribute and maintain packages. Do you think this would be a good idea? If so, I would love to work on it (I am familiar with Go, Rust and Python).

    Thank you,
    Jeremy (jwinnie)


    --
    Mechtilde Stehmann
    ## Apache OpenOffice
    ## Freie Office Suite für Linux, MacOSX, Windows und OS/2
    ## Debian Developer
    ## PGP encryption welcome
    ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F


    --il4vOcL3NWEVCXrzMcAHy45Z3jFI0D9Qq--

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

    iQIzBAEBCgAdFiEE8ON/Pch6SZgomTnn8od7uhQarX8FAmB7yiAACgkQ8od7uhQa rX+cRBAAh2No6CeEbexlcH3YY5+bllB84MsbRUGz8OXx6zhq6Ed6z0hyvvvduJ0a GRe5VrMSio6MXthj3Fzi/MTcJVgb4jMja6e6ngbQ291kYKdIi6kZ4WLpjzwLy6NG LWc/vUPITmLH57lG3ehsClselAb82BsdtjpOU/hSVJx5SNnL3BND1iMwQLIyT0CR UbXUu78RVVB3A7en8AsnjYd6mnIU969aPWzAHrn8ksbOVr2sCbaZ+XvmAHiwsZSB 5Sp8hXWXj8ctyu7iNZ0VwBNNDL2EZFjQQ1tYUbUudIm+pbXjhm2vmGj2+emDWas+ xp7sQHWiKyuHTvJiqYkb+h5fVF/IPQ5sHckd5k2OzyZQ0PerpWjQJTrPRBb62IGu PPSq4MmynBlzgBjItimQKdhqknEXlmN5di8QuKF6bDomEByemO5wwSb+mVCnne/l 3f/3ChdYBEwAtu76zrqOmUHff/upeKY/79ixqiB9CWnLHyPT5styJkD83zI8+Nfy WCMqGcKm146DxQFk+CUn8+t9GG7btP/gu8rIJTHjAXFa4aCg+8YcgekwfoHLmyQj oCRaGto4Ug3tlF6PJGGL/UdQ44nYOGfXOaCGVnrZaUa9665nRSF4UwBk22jh1HlJ
    aDhZUx7+NR
  • From Aoki, Osamu@21:1/5 to Mechtilde on Tue Apr 20 15:00:03 2021
    HI,

    On Sun, 2021-04-18 at 07:56 +0200, Mechtilde wrote:
    Hello Jeremy,

    I already try to do so.

    I'm writing a shell script to automate the build process as far as possible.

    And I'm documenting it literally.

    I do it in German and it is prepared for translation.

    Source: https://salsa.debian.org/ddp-team/dpb

    Book: https://people.debian.org/~mechtilde/Dokumentatio
    Cooperation is welcome.

    Looks interesting.

    Have you thought about improving existing ones.

    https://www.debian.org/doc/devel-manuals#debmake-doc

    or even its previous version.

    https://www.debian.org/doc/devel-manuals#maint-guide

    They already come with translations.

    Very verbose documentation doesn't help much since we are working on
    the moving target.

    Biggest shortcomings are:

    They don't use the current sbuild.
    They are not updated on time.

    I think gbp will stay here but the use of dgit will increase. For the
    chroot build system, there is not much reason not to use sbuild.  

    After all, it share the same build system as the official buildd.
    It uses overlay mount and it is supported by kernel for good long time
    and we can use any filesystem. (NO LVM or Btrfs required.) (Except "I
    don't like Perl" like me. Well, I even had to work on uscan in Perl to
    be useful to others.)

    https://wiki.debian.org/sbuild

    I will change https://www.debian.org/doc/devel-manuals#debmake-doc
    to use sbuild after bullseye. https://salsa.debian.org/debian/debmake-doc/-/tree/sbuild

    It is non-trivial to do piupitus and autopkgtest with
    pbuilder/cowbuilder. gbp can be used with sbuild now.

    apt-cache-ng has some issue for deb.debian.org in its chroot apt line
    but I think that can be adddressed ...

    https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986356

    Regards,

    Osamu

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mechtilde Stehmann@21:1/5 to Aoki, Osamu on Tue Apr 20 15:40:02 2021
    To: debian-mentors@lists.debian.org

    This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --kZRS0qCuLjf0oE0ZKnUoXOqxmiRwVVrXi
    Content-Type: text/plain; charset=utf-8
    Content-Language: en-US
    Content-Transfer-Encoding: quoted-printable

    Hello

    Am 20.04.21 um 14:52 schrieb Aoki, Osamu:
    HI,

    On Sun, 2021-04-18 at 07:56 +0200, Mechtilde wrote:
    Hello Jeremy,

    I already try to do so.

    I'm writing a shell script to automate the build process as far as possible. >>
    And I'm documenting it literally.

    I do it in German and it is prepared for translation.

    Source: https://salsa.debian.org/ddp-team/dpb

    Book: https://people.debian.org/~mechtilde/Dokumentatio
    Cooperation is welcome.

    Looks interesting.

    Have you thought about improving existing ones.

    https://www.debian.org/doc/devel-manuals#debmake-doc

    or even its previous version.

    https://www.debian.org/doc/devel-manuals#maint-guide
    Yes, but I can't do it.

    My starting point was my try to automate the packaging process.

    I tried do document all those steps which I find out by try and error,
    reading many documents from different sources and try and error again.

    They already come with translations.

    Very verbose documentation doesn't help much since we are working on
    the moving target.

    Biggest shortcomings are:

    They don't use the current sbuild.
    They are not updated on time.

    As long as I haven't any idea ow sbuild works and/or what are the
    different and how it changes the part I described, I can't describe it.

    I think gbp will stay here but the use of dgit will increase. For the
    chroot build system, there is not much reason not to use sbuild.  

    After all, it share the same build system as the official buildd.
    It uses overlay mount and it is supported by kernel for good long time
    and we can use any filesystem. (NO LVM or Btrfs required.) (Except "I
    don't like Perl" like me. Well, I even had to work on uscan in Perl to
    be useful to others.)

    https://wiki.debian.org/sbuild

    I will change https://www.debian.org/doc/devel-manuals#debmake-doc
    to use sbuild after bullseye. https://salsa.debian.org/debian/debmake-doc/-/tree/sbuild

    It is non-trivial to do piupitus and autopkgtest with
    pbuilder/cowbuilder. gbp can be used with sbuild now.

    apt-cache-ng has some issue for deb.debian.org in its chroot apt line
    but I think that can be adddressed ...

    https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986356

    My goal is to help people to understand why packaging for a distribution
    and here esp for Debian is important and very interesting.


    Regards,

    Osamu



    Kind regards

    --
    Mechtilde Stehmann
    ## Debian Developer
    ## PGP encryption welcome
    ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F


    --kZRS0qCuLjf0oE0ZKnUoXOqxmiRwVVrXi--

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

    iQIzBAEBCgAdFiEE8ON/Pch6SZgomTnn8od7uhQarX8FAmB+2HoACgkQ8od7uhQa rX/ssg/9F9LGJfywTEoUvridHw+8Haxd3JU3SGllfYhXalGPAMSWp9AXICv8fM92 jKyW3U0UZR4uYCqpdXK7kkdARZ4W8Pnmm88V+5qJo0Xaid2J3OOhetH7+EPwWhRY y0Zu5rRAPSvfsTUSkStRFvfu5O+rQ2EASrj7LXDiSiHvJZhaU2u+GOF/t6V5G8qe 12CMgjJW/thDGjrWj8tgUz5KCG84r46EWgWmWM7kuMwh6Z7KIhvjCU0giCNAyjlC i0WzdVwBvhQ5CBmsnnScwqfhg4IHp7HekOwBIp16YXOz9nGRsO19vlgEg7B1hz9Y joB1NN6b3VRosb7DBTloC/61YnxyQHdrRmHTAsmDgN82Mhrkbuk9YYJBjo9kJQ84 1vCQvFo0oW6lHOYpFH7FKL7+zi/1aENjjvIJK+KPxNS87mgm/MZ7ENZyBVku/b1t fPDWQJYlFHQtndKmrffdXnZXo3NRKC85JblI1XP0McUAHEnEQXuuAC38zDKrtQ3d cQI/VTaTfpREfFaQLf8RBEcXKPxDjT5JXsmPWypO6/zYH/HoiiuSCh/SUgWTRZ3q N+c7VOdy4udwxFgFVOs9WCytWFVoIwLCgjlFlqF5XzK+5HfHNElpn7WZ/bawfxi9 T5VKNvk3ayKtl5SRqgAO5RO2vMQLXQtDL3AV66tuRsmlorZ/TEk=
    =6mt+
    -----END PGP SIGNATURE-----