Re: flashrom_1.3.0-3_source.changes ACCEPTED into unstable
Ummm.
We appear to have conflicting histories in the git repo for flashrom,
on the debian and master branches.
I also don't see this 1.3.0-3 release in git at all.
Could we agree on history and sort this out please?
On Tue, Jul 16, 2024 at 03:05:37PM +0000, Debian FTP Masters wrote:
>Thank you for your contribution to Debian.
>
>
>
>Accepted:
>
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA256
>
>Format: 1.8
>Date: Tue, 16 Jul 2024 14:29:29 +0000
>Source: flashrom
>Architecture: source
>Version: 1.3.0-3
>Distribution: unstable
>Urgency: medium
>Maintainer: Debian EFI <debian-efi@lists.debian.org>
>Changed-By: Alex Myczko <tar@debian.org>
>Changes:
> flashrom (1.3.0-3) unstable; urgency=medium
> .
> * Ack NMU.
> * Bump standards version to 4.7.0.
> * d/control: update build depends pkg-config to pkgconf.
>Checksums-Sha1:
> 9c4c09ced20b62ed0736843856fd7e0e007bf98a 2196 flashrom_1.3.0-3.dsc
> 7074df4b53c3dec7d0b196449b023f5b7cfb6f7e 11176 flashrom_1.3.0-3.debian.tar.xz
> 257bae349180927771ad7ae3df0b81748032f80f 8363 flashrom_1.3.0-3_source.buildinfo
>Checksums-Sha256:
> 66a86b78c706743dd2967488b483cbcd907d943c3b5a238849e0ed7735e9542b 2196 flashrom_1.3.0-3.dsc
> 591fba57b71492492c121b2642cbe1c8074ec87c1aedb2d2f5a3f849d1619354 11176 flashrom_1.3.0-3.debian.tar.xz
> 1d800f6f147c33f6e71bc81d444cc2129c65a26d1675b3706b4bc73e7e552eea 8363 flashrom_1.3.0-3_source.buildinfo
>Files:
> 50c8f09a6bd668d9940a6cddab016c88 2196 electronics optional flashrom_1.3.0-3.dsc
> bc57ccb1c9a4196d719263061b7a27df 11176 electronics optional flashrom_1.3.0-3.debian.tar.xz
> 1a099580c4c0fbd0b1ead24d2eaf23a6 8363 electronics optional flashrom_1.3.0-3_source.buildinfo
>
>-----BEGIN PGP SIGNATURE-----
>
>iQIzBAEBCAAdFiEEtgob82PcExn/Co6JEWhSvN91FcAFAmaWhxQACgkQEWhSvN91
>FcAZxg//XGUMlpxOpJSjOxcBrkUTutXCCBYSoVgQyGs0DFUhhattZxm9RxTJYMcb
>U1dg9BbMRq5rc7FzE+iO7/vArGyU9oc58XN+b7vrwgxc12a7AzrggZr4/gUPzSQC
>AOXYBOPTnZ1Ir99kiSrjk6l+aY4cq9D/Mx7J7UiEzRLfKL7wy1xfhFAoiUZrKjUf
>eib/NDWA3sq8Wd/Vp2kfq5mCBXkSm6pxFIY5ag2OaOfCCtmu9NDL0JFDu/R4KwCl
>Y1Rmhdmf6VrkdHGM0cW6QwfXqZE+/3gyGLHja/O658fS7bOekNKqt9qlcTKwogGL
>Phal8M8YQ4S0RgdFUeUmX/StsrTotR5NSv2EEQIebdMxxiqUSOAkMen3KZOBDn+w
>lKetDTkeBLcMj8E+OITz/jG9NrP+QlVwkycNNjr6AHJ/JhugSk5Fhy6ca2Pl4wgx
>KlNF0GjGKXDV3/n/KJTSGd+mxIY7bwZVocWZJPgljFlyGeRG7MGjOIc28pUtxyIT
>ZWX+cAPoCkyoj43Qf3xT0TCq/bJOokwIkvL+DEYNe5rzcQ3qbQX2yv87BJm3oExH
>PAxqI9oqqwa/RQ8knuxoxyCAw/4CHszhXrMZwbHrfE7LIRkEN1GMGhFDC7du6cbz
>k55tHyfeEE9JNfWg8jbssJeS/1tedyf0lWINnvDBKbvcS8iWqUI=
>=Me8x
>-----END PGP SIGNATURE-----
>
--
Steve McIntyre, Cambridge, UK. steve@einval.com
“Why do people find DNS so difficult? It’s just cache invalidation and
naming things.”
-– Jeff Waugh (https://twitter.com/jdub)
Reply to: