Your message dated Tue, 11 Feb 2025 23:07:12 +0000
with message-id <e1thzlu-0062xq...@fasolo.debian.org>
and subject line Bug#1026018: fixed in kustomize 5.5.0+ds-1
has caused the Debian Bug report #1026018,
regarding ITP: kustomize -- Customization of kubernetes YAML configurations
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.)


-- 
1026018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026018
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: sun min <sunmi...@outlook.com>
X-Debbugs-Cc: debian-de...@lists.debian.org, debian...@lists.debian.org

* Package name    : kustomize
  Version         : 3.3.1-1
  Upstream Author : Kubernetes SIGs
* URL             : https://github.com/kubernetes-sigs/kustomize
* License         : Apache-2.0
  Programming Lang: Go
  Description     : Customization of kubernetes YAML configurations

 kustomize
 .
 kustomize lets you customize raw, template-free YAML files for multiple
 purposes, leaving the original YAML untouched and usable as is.
 .
 kustomize targets kubernetes; it understands and can patch kubernetes
 style
 (https://kubectl.docs.kubernetes.io/references/kustomize/glossary/#kubernetes-
 style-object) API objects.  It's like make
 (https://www.gnu.org/software/make), in that what it does is declared in
 a file, and it's like sed (https://www.gnu.org/software/sed), in that it
 emits edited text.
 .
 This tool is sponsored by sig-cli
 (https://github.com/kubernetes/community/blob/master/sig-cli/README.md)
 (KEP (https://github.com/kubernetes/enhancements/blob/master/keps/sig-
 cli/2377-Kustomize/README.md)).
 .
  * Installation instructions
    (https://kubectl.docs.kubernetes.io/installation/kustomize/)
  * General documentation
    (https://kubectl.docs.kubernetes.io/references/kustomize/)
  * Examples (/examples)
 .
 Build Status (https://prow.k8s.io/job-history/kubernetes-jenkins/pr-
 logs/directory/kustomize-presubmit-master) Go Report Card
 (https://goreportcard.com/report/github.com/kubernetes-sigs/kustomize)
 .
 kubectl integration
 .
 The kustomize build flow at v2.0.3 (https://github.com/kubernetes-
 sigs/kustomize/releases/tag/v2.0.3) was added to kubectl v1.14
 (https://kubernetes.io/blog/2019/03/25/kubernetes-1-14-release-
 announcement).  The kustomize flow in kubectl remained frozen at v2.0.3
 until kubectl v1.21, which updated it to v4.0.5
 
(https://github.com/kubernetes/kubernetes/blob/4d75a6238a6e330337526e0513e67d02b1940b63/CHANGELOG/CHANGELOG-
 1.21.md#kustomize-updates-in-kubectl). It will be updated on a regular
 basis going forward, and such updates will be reflected in the
 Kubernetes release notes.
 .
   KUBECTL VERSION | KUSTOMIZE VERSION
 ------------------+--------------------
   < v1.14         | n/a
   v1.14-v1.20     | v2.0.3
   v1.21           | v4.0.5
   v1.22           | v4.2.0
 .
 For examples and guides for using the kubectl integration please see the
 kubernetes documentation (https://kubernetes.io/docs/tasks/manage-
 kubernetes-objects/kustomization/).
 .
 Usage
 .
 1) Make a kustomization
 
(https://kubectl.docs.kubernetes.io/references/kustomize/glossary/#kustomization)
 file
 .
 In some directory containing your YAML resource
 (https://kubectl.docs.kubernetes.io/references/kustomize/glossary/#resource)
 files (deployments, services, configmaps, etc.), create a kustomization
 
(https://kubectl.docs.kubernetes.io/references/kustomize/glossary/#kustomization)
 file.
 .
 This file should declare those resources, and any customization to apply
 to them, e.g. *add a commonlabel*.
 .
 [Image: base image] (/images/base.jpg)
 .
 File structure:
 .
  |
 .
 The resources in this directory could be a fork of someone else's
 configuration.  If so, you can easily rebase from the source material to
 capture improvements, because you don't modify the resources directly.
 .
 Generate customized YAML with:
 .
   kustomize build ~/someApp
 .
 The YAML can be directly applied
 (https://kubectl.docs.kubernetes.io/references/kustomize/glossary/#apply)
 to a cluster:
 .
  |
 .
 2) Create variants
 (https://kubectl.docs.kubernetes.io/references/kustomize/glossary/#variant)
 using overlays
 (https://kubectl.docs.kubernetes.io/references/kustomize/glossary/#overlay)
 .
 Manage traditional variants
 (https://kubectl.docs.kubernetes.io/references/kustomize/glossary/#variant)
 of a configuration - like *development*, *staging* and *production* -
 using overlays
 (https://kubectl.docs.kubernetes.io/references/kustomize/glossary/#overlay)
 that modify a common base
 (https://kubectl.docs.kubernetes.io/references/kustomize/glossary/#base).
 .
 [Image: overlay image] (/images/overlay.jpg)
 .
 File structure:
 .
  |
 .
 Take the work from step (1) above, move it into a someApp subdirectory
 called base, then place overlays in a sibling directory.
 .
 An overlay is just another kustomization, referring to the base, and
 referring to patches to apply to that base.
 .
 This arrangement makes it easy to manage your configuration with git.
 The base could have files from an upstream repository managed by someone
 else. The overlays could be in a repository you own. Arranging the repo
 clones as siblings on disk avoids the need for git submodules (though
 that works fine, if you are a submodule fan).
 .
 Generate YAML with
 .
   kustomize build ~/someApp/overlays/production
 .
 The YAML can be directly applied
 (https://kubectl.docs.kubernetes.io/references/kustomize/glossary/#apply)
 to a cluster:
 .
  |
 .
 Community
 .
  * file a bug
    (https://kubectl.docs.kubernetes.io/contributing/kustomize/bugs/)
  * contribute a feature
    (https://kubectl.docs.kubernetes.io/contributing/kustomize/features/)
  * propose a larger enhancement (https://github.com/kubernetes-
    sigs/kustomize/tree/master/proposals)
 .
 Code of conduct
 .
 Participation in the Kubernetes community is governed by the Kubernetes
 Code of Conduct (/code-of-conduct.md).

--- End Message ---
--- Begin Message ---
Source: kustomize
Source-Version: 5.5.0+ds-1
Done: Arthur Diniz <arthurbdi...@gmail.com>

We believe that the bug you reported is fixed in the latest version of
kustomize, 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 1026...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Arthur Diniz <arthurbdi...@gmail.com> (supplier of updated kustomize 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: SHA512

Format: 1.8
Date: Mon, 16 Dec 2024 19:54:14 +0000
Source: kustomize
Binary: golang-k8s-sigs-kustomize-dev kustomize kustomize-dbgsym
Architecture: source all amd64
Version: 5.5.0+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kubernetes Packaging Team 
<team+kuberne...@tracker.debian.org>
Changed-By: Arthur Diniz <arthurbdi...@gmail.com>
Description:
 golang-k8s-sigs-kustomize-dev - Customization of Kubernetes YAML 
configurations (library)
 kustomize  - Customization of Kubernetes YAML configurations (program)
Closes: 1026018
Changes:
 kustomize (5.5.0+ds-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #1026018)
Checksums-Sha1:
 1c65910542fe1cf230b34ce5fd36b99058fa2290 2502 kustomize_5.5.0+ds-1.dsc
 d01392830f4eda3f855f7c65e1097f58b62bcf1d 170800 kustomize_5.5.0+ds.orig.tar.xz
 4712bb58c810c9fa80c83bf9b7867270ee963afe 3096 
kustomize_5.5.0+ds-1.debian.tar.xz
 9099bd6dcc1552608c9475a54f6f45ee5f9a9f13 52044 
golang-k8s-sigs-kustomize-dev_5.5.0+ds-1_all.deb
 8a8f39f28b5a5ea6db0f7610b3d9ce8020527334 5601112 
kustomize-dbgsym_5.5.0+ds-1_amd64.deb
 4c2a92cab6fef2dc4e26e1f4d2ab95a706e44681 11835 
kustomize_5.5.0+ds-1_amd64.buildinfo
 da2a132c4488e9f47dbfc98675122ed0958893eb 5874732 kustomize_5.5.0+ds-1_amd64.deb
Checksums-Sha256:
 6e735afaf7845bc88750cddf3612083e9a1615d7e8e2120ce88d66acf60a1b1d 2502 
kustomize_5.5.0+ds-1.dsc
 b0d402024559c3f1e7904df9336d6b799af7d9cf1023a02238c0e7421c836473 170800 
kustomize_5.5.0+ds.orig.tar.xz
 a7167208e711cc8f817db0b63636eac5886cad7181f8e86e80c9a44b294224df 3096 
kustomize_5.5.0+ds-1.debian.tar.xz
 a6a7be6ad3c2bad65645bc5ae0c50dd87c8e4087cec6b7cf0f46dcd5d900af4b 52044 
golang-k8s-sigs-kustomize-dev_5.5.0+ds-1_all.deb
 b4dc3a904025606ac61892f20d8638e31bb902278166c2522ff8f3e151817efe 5601112 
kustomize-dbgsym_5.5.0+ds-1_amd64.deb
 59b9af7fef06557128a9327f756e4ca3974b1813b20d864d0ee96eca9e755d80 11835 
kustomize_5.5.0+ds-1_amd64.buildinfo
 973cdc5be3bc318ab71310fbfc43384a3763340498b27c4213dcfb635a7f20d9 5874732 
kustomize_5.5.0+ds-1_amd64.deb
Files:
 78ddfcc22cfe45ec766c1f331d356310 2502 golang optional kustomize_5.5.0+ds-1.dsc
 0a04f33751f55776661593433e99dcb7 170800 golang optional 
kustomize_5.5.0+ds.orig.tar.xz
 630bf960d3e8b245463db033b782b3ea 3096 golang optional 
kustomize_5.5.0+ds-1.debian.tar.xz
 a47872188e45e62d07f56ba2ae383d55 52044 golang optional 
golang-k8s-sigs-kustomize-dev_5.5.0+ds-1_all.deb
 7bcbbaf345e4529c2184fdba80a31866 5601112 debug optional 
kustomize-dbgsym_5.5.0+ds-1_amd64.deb
 f4afa1bfbd518fc97b42967adfe2d60c 11835 golang optional 
kustomize_5.5.0+ds-1_amd64.buildinfo
 58e0303d8d90514b5cc95f5d8efbd9c8 5874732 golang optional 
kustomize_5.5.0+ds-1_amd64.deb

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

iQIzBAEBCgAdFiEEBdtqg34QX0sdAsVfu6n6rcz7RwcFAmecDYUACgkQu6n6rcz7
Rwchtw/+LipwjZz1aflQP1umGMNOizxT4fn9pD0pe3kptvwRcIxFoLOnOpmKNvrM
ykCeCDzOfrnMsdrAzORebCg0d+sMbUlnFmcN6+Jv16YHsAHs7sxhH0gqipp8Pg1O
fGOuTSlzdmA5TBtyB5+Csxd++HT5af4UzN2Rviq9qmQtIoZm0IJiPH+ftNgcshsL
GJ3+T5v+1dsdVlUzv6XNUqVntjg3J3DH5+/Uj3Qg+dwfmBbteYL3hX3uLSR53rdJ
XEEItXraZz6sugZB60UqXT9IdmX50zH+RbLBJTmh+Q3AwtEQZu71xzK8TndbVW8E
v0CduBX6Z901u/Q6AdIu7U1P4t0e3Nosrxr8JUXN49Kud9VipLJKTewFizu0LNj8
mjD7JwZ0sErVysO9gQJxZPCeBKSNMOrvQb6XSMUP70VvfVgJ1bHiG/5qiQffTK1q
mEpAkFK9/JSM1X+WV8BHjfGhCNzwI7PneBMsleFRsQCNqGNXHXPdMqvg/4wHIjdI
lPWHKJsAgei84T8zTtn5sdyDsJqTQmpqWwKpxjVEImKKJXmETqwfg0V5SsGZdUIV
0FlaJbt3rNwdsaSNg1DcdthNEx6Rguz9npjOAl7LfZknvMavXOeNP7yP0zPRCfp6
9s5krSW09JrTYPHRTc9QFh/CnnpUv8QsT8NS67mpz7x/Cuv1mjE=
=BbAK
-----END PGP SIGNATURE-----

Attachment: pgpGYq2NMgrvw.pgp
Description: PGP signature


--- End Message ---

Reply via email to