Bug#934183: buster-pu: package open-vm-tools/2:10.3.10-1+deb10u1
On 8/18/19 4:35 PM, Adam D. Barratt wrote: > On Wed, 2019-08-07 at 21:44 +0200, Bernd Zeimetz wrote: >> I'd like to upload a fix for open-vm-tools to proposed-updates which >> actually allows to recognize buster. >> >> `lsb_release -sd` currently prints >> Debian GNU/Linux 10 (buster) >> but the current implementation in open-vm-tools expects 10. in the >> output. > > Please go ahead; thanks. Uploaded. Thanks, Bend -- Bernd ZeimetzDebian GNU/Linux Developer http://bzed.dehttp://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F
Bug#934368: transition: x265
On 2019-08-18 17:58:59, Jonathan Wiltshire wrote: > > As usual, libx265 bumped its SONAME. All reverse dependencies build fine > > against the new version. Please let me know once it's a good time to > > upload the new version from experimental to unstable. > > Please go ahead. Thanks, uploaded. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#933125: buster-pu: package systemd/241-5+deb10u1
Hi Adam Am 16.08.19 um 22:08 schrieb Adam D. Barratt: > Control: tags -1 + confirmed > > On Fri, 2019-07-26 at 21:43 +0200, Michael Biebl wrote: >> I'd like to make a stable upload for systemd, fixing the following >> issues: > [...] >> 241-5+deb10u1 is identical to 241-7 which has been uploaded to >> unstable/bullseye and we haven't received any regression reports so >> far. > > In that case, feel free to make it -7~deb10u1, with the appropriate > changelog wrangling, if that would be preferable. I considered adding a changelog entry like this as it seemed the most obvious correct one: --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +systemd (241-7~deb10u1) buster; urgency=medium + + * Rebuild for buster + + -- Michael Biebl Sat, 17 Aug 2019 11:00:59 +0200 + systemd (241-7) unstable; urgency=medium [ Michael Biebl ] But this then triggers warnings from dpkg-genchanges: dpkg-genchanges: warning: the current version (241-7~deb10u1) is earlier than the previous one (241-7) and lintian: W: systemd: latest-debian-changelog-entry-without-new-version To avoid that, I could rewrite the old changelog entry for 241-7 like this --- a/debian/changelog +++ b/debian/changelog @@ -1,4 +1,4 @@ -systemd (241-7) unstable; urgency=medium +systemd (241-7~deb10u1) buster; urgency=medium [ Michael Biebl ] * network: Fix failure to bring up interface with Linux kernel 5.2. Rewriting the old changelog entry for 241-7 feels wrong though. Adam, so I wonder, what's the proper changelog wrangling in this case? Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#934368: transition: x265
Control: tag -1 confirmed On Sat, Aug 10, 2019 at 10:47:03AM +0200, Sebastian Ramacher wrote: > As usual, libx265 bumped its SONAME. All reverse dependencies build fine > against the new version. Please let me know once it's a good time to > upload the new version from experimental to unstable. Please go ahead. -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
Processed: Re: Bug#934368: transition: x265
Processing control commands: > tag -1 confirmed Bug #934368 [release.debian.org] transition: x265 Added tag(s) confirmed. -- 934368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934368 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 934112
Processing commands for cont...@bugs.debian.org: > close 934112 Bug #934112 [release.debian.org] transition: poco Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 934112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934112 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#931551: transition: llvm-defaults to 8
Control: tag -1 confirmed On Sun, Jul 07, 2019 at 04:29:31PM +0200, Sylvestre Ledru wrote: > Now that we release buster, I would like to move llvm-defaults to > llvm-toolchain-8. Ok, let's go! Thanks, -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
Processed: Re: Bug#931551: transition: llvm-defaults to 8
Processing control commands: > tag -1 confirmed Bug #931551 [release.debian.org] transition: llvm-defaults to 8 Added tag(s) confirmed. -- 931551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931551 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: Bits from the Release Team: ride like the wind, Bullseye!
On Sun, Aug 18, 2019 at 08:54:21AM +0100, Ian Jackson wrote: > > On 19/08/08 09:46, Paul Gevers wrote: > > > I think we should also try to improve the visibility towards reverse > > > dependencies that their autopkgtest is blocking other packages. I would > > > love tracker (and the old pts) to show this on their page. (Working on > > > such a patch is on my TODO list, except not at the top). > > I already made grep-excuses print this information. It has been very > helpful to me. Maybe we should make --autopkgtests the default ? I think no: --autopkgtests requires quite a bit more computation and connecting to udd and whatnot, I don't think that should be the default. Especially because udd-mirror is starting to be under-dimensioned so it's sometimes quite slow to serve responses (like in the times when its importing a new dump). -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Re: Bug#933002: docker.io: CVE-2019-13139
On Sun, 2019-08-18 at 16:56 +0200, Arnaud Rebillout wrote: > * The bug you want to fix in stable must be fixed in unstable > already (and not waiting in NEW or the delayed queue) > > My issue with this particular bug (#933002) is that for now, > docker.io doesn't build in unstable. It will take a while before it > builds again, as there was changes in the dependency tree. > > On the other hand, fixing this bug in stable is just a matter of > importing the patch from upstream and rebuilding the package. > > So how am I supposed to handle that? Waiting for docker.io to be > fixed and built again in unstable will delay the fix in stable for > weeks, I don't think it's a good option. Nevertheless, that is the case I'm afraid. Updates to stable via proposed-updates are not appropriate for urgent security updates - that is what the security archive is for. Looking at https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=docker.io , there doesn't appear to be a bug filed for the build failure, so there's no indication of what the issues are, nor what needs to be done to fix them. Regards, Adam
Re: Bug#933002: docker.io: CVE-2019-13139
Dear Release Team, I'm new to the process of uploading to stable, I need your guidance on that one. From the buster announce: * The bug you want to fix in stable must be fixed in unstable already (and not waiting in NEW or the delayed queue) My issue with this particular bug (#933002) is that for now, docker.io doesn't build in unstable. It will take a while before it builds again, as there was changes in the dependency tree. On the other hand, fixing this bug in stable is just a matter of importing the patch from upstream and rebuilding the package. So how am I supposed to handle that? Waiting for docker.io to be fixed and built again in unstable will delay the fix in stable for weeks, I don't think it's a good option. Best regards, Arnaud
Bug#933793: stretch-pu: package usbutils/1:007-4+deb9u1
On 2019-08-18 15:27, Adam D. Barratt wrote: > On Sat, 2019-08-03 at 16:42 +0200, Aurelien Jarno wrote: > > I would like to update usbutils in stretch to update the usb.ids > > database. There is no code change, the changes only adds a few > > hundred of USB devices to the database. There are a lot of new > > entries as this hasn't been updated for quite some time. Those > > changes are already in bullseye and sid. > > > > I have already uploaded the package to stretch-pu, the full diff is > > attached. Thanks for considering. > > The upload doesn't seem to have made it to oldstable-new yet, and I > can't spot it in the logs on upload.d.o. Hmm, indeed it seems i have prepared the upload but I haven't actually done the upload. I just did that now. Thanks, Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Processed: Re: Bug#934163: buster-pu: package ncurses/6.1+20181013-2+deb10u1
Processing control commands: > tags -1 + confirmed d-i Bug #934163 [release.debian.org] buster-pu: package ncurses/6.1+20181013-2+deb10u1 Added tag(s) confirmed. -- 934163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934163 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#934206: buster-pu: package golang-github-docker-docker-credential-helpers/0.6.1-2+deb10u1
On 8/16/19 9:35 PM, Adam D. Barratt wrote: So is the conclusion there that docker.io is or is not actually affected? Yes docker.io is affected as well.
Bug#934163: buster-pu: package ncurses/6.1+20181013-2+deb10u1
Control: tags -1 + confirmed d-i On Wed, 2019-08-07 at 18:01 +0200, Sven Joachim wrote: > I have just uploaded ncurses 6.1+20181013-2+deb10u1 to Buster which > contains a one-line fix for bug #933053[1], the same as in version > 6.1+20190713-2 which is now in testing. > > Some background: for about 20 years, xterm has support for a special > escape sequence which causes characters to be repeated. In ncurses > 6.1-1 and later, an entry was added to the xterm* terminfo > descriptions announcing this feature. The ncurses library makes use > of it for line drawing characters. Looks OK to me, thanks; just needs the d-i ack. Regards, Adam
Bug#934183: buster-pu: package open-vm-tools/2:10.3.10-1+deb10u1
On Wed, 2019-08-07 at 21:44 +0200, Bernd Zeimetz wrote: > I'd like to upload a fix for open-vm-tools to proposed-updates which > actually allows to recognize buster. > > `lsb_release -sd` currently prints > Debian GNU/Linux 10 (buster) > but the current implementation in open-vm-tools expects 10. in the > output. Please go ahead; thanks. Regards, Adam
Bug#934952: stretch-pu: package icu/57.1-6+deb9u3
Control: tags -1 + confirmed On Sat, 2019-08-17 at 10:20 +0200, László Böszörményi wrote: > There's a crash in Stretch with ICU, there's a missing NULL check in > the LocalArray class. It crashes ICU with certain options / use > case[1]. Upstream fixed it[2] and now I would like to make it to > Stretch. > Please go ahead. Regards, Adam
Processed: Re: Bug#934952: stretch-pu: package icu/57.1-6+deb9u3
Processing control commands: > tags -1 + confirmed Bug #934952 [release.debian.org] stretch-pu: package icu/57.1-6+deb9u3 Added tag(s) confirmed. -- 934952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934952 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#934956: buster-pu: package cryptsetup/2:2.1.0-5+deb10u1
Processing control commands: > tags -1 + confirmed d-i Bug #934956 [release.debian.org] buster-pu: package cryptsetup/2:2.1.0-5+deb10u1 Added tag(s) d-i and confirmed. -- 934956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934956 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#934956: buster-pu: package cryptsetup/2:2.1.0-5+deb10u1
Control: tags -1 + confirmed d-i On Sat, 2019-08-17 at 11:03 +0200, Guilhem Moulin wrote: > Buster's cryptsetup (2:2.1.0-5) doesn't cope well with LUKS2 headers > without any bound keyslot: adding a new key slot to such a header > fails, both via the crypt_keyslot_add_by_volume_key() API call and > with `luksAddKey --master-key`. [...] > The 3 cherry-picked patches are all backported from 2.2.0 [1,2], and > the > version in sid is not affected. (The one in Stretch is not affected > either as it doesn't have LUKS2 support.) Looks OK to me, thanks; just needs the d-i ack. Regards, Adam
Bug#933793: stretch-pu: package usbutils/1:007-4+deb9u1
On Sat, 2019-08-03 at 16:42 +0200, Aurelien Jarno wrote: > I would like to update usbutils in stretch to update the usb.ids > database. There is no code change, the changes only adds a few > hundred of USB devices to the database. There are a lot of new > entries as this hasn't been updated for quite some time. Those > changes are already in bullseye and sid. > > I have already uploaded the package to stretch-pu, the full diff is > attached. Thanks for considering. The upload doesn't seem to have made it to oldstable-new yet, and I can't spot it in the logs on upload.d.o. Regards, Adam
Bug#934872: marked as done (RM: ocaml-usb/1.3.0-4 ocaml-sqlexpr/0.5.5-3 zeroinstall-injector/2.12.3-2 obus/1.1.5-6)
Your message dated Sun, 18 Aug 2019 15:26:14 +0200 with message-id <54380ddc-3434-49e3-12af-0a72393e0...@debian.org> and subject line Re: Bug#934872: RM: ocaml-usb/1.3.0-4 ocaml-sqlexpr/0.5.5-3 zeroinstall-injector/2.12.3-2 obus/1.1.5-6 has caused the Debian Bug report #934872, regarding RM: ocaml-usb/1.3.0-4 ocaml-sqlexpr/0.5.5-3 zeroinstall-injector/2.12.3-2 obus/1.1.5-6 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.) -- 934872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934872 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Dear Release Managers, Please remove the following packages from testing: * ocaml-usb, affected by #933993 * ocaml-sqlexpr, affected by #933994 * zeroinstall-injector, affected by #934340 * obus, affected by #933992 They prevent 62 other packages from migrating to testing. They are already marked for autoremoval, but too far in the future. Cheers, -- Stéphane -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Le 16/08/2019 à 06:39, Stéphane Glondu a écrit : > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: rm > > Dear Release Managers, > > Please remove the following packages from testing: > > * ocaml-usb, affected by #933993 > * ocaml-sqlexpr, affected by #933994 > * zeroinstall-injector, affected by #934340 > * obus, affected by #933992 > > They prevent 62 other packages from migrating to testing. They are > already marked for autoremoval, but too far in the future. From #debian-release: [15:17] sgnb: I added a removal hint. Can you close the rm bug? Cheers, -- Stéphane--- End Message ---
Bug#935028: marked as done (nmu: lutok_0.4+dfsg-1)
Your message dated Sun, 18 Aug 2019 12:18:40 +0100 with message-id <1566127120.5665.11.ca...@adam-barratt.org.uk> and subject line Re: Bug#935028: nmu: lutok_0.4+dfsg-1 has caused the Debian Bug report #935028, regarding nmu: lutok_0.4+dfsg-1 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.) -- 935028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935028 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 nmu lutok_0.4+dfsg-1 . all amd64 . unstable . -m "Rebuild on buildd for transition to bullseye" - -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEU7EqA8ZVHYoLJhPE5vmO4pLV7MsFAl1ZHWcRHG5pY29vQGRl Ymlhbi5vcmcACgkQ5vmO4pLV7Mtb0A//R48O/DONlsLBGW4ZyelG+WnO8RTtf9oV CScKgbfvSQGfQjbVucnLtgff22QexedUdkkNOIEaWSsqNvvhXFU+VFbTv2YwyHFI Bc2l0eGHy9YzxJhUppdiNQvyzwO2RNS8b1htcQp7HVCJ9knzrldA4mUhlmGUfSbY SVVI6/efAvCniyRePvQxsE10ugbMQwAkhbkf0zRixtC+5jv7NkK2rcVPQZqOlmG8 w6ZjElU90wbpf/ZHcE1MftTBPkERyN5OlvWAhMBxYaTzCTZZRSFpcds/DscWMQXp EWwyg1Xa6MSHfz9MJUT57qKtu95we6yRmzzLeC0wrC5RrDEHTayurTM+e+UZEsA0 D2idzZTvvWZxYGmvBoRTUj8BFGmJD5QWKMVmqHwdOSd7GIhJoTmflDB6Pv17le1I cCKv+IJ0wJDef8ls8DnHjHZ5saBzmZtQRZH8JD9Aj7/rP9epGiNQ0fEuJ6oR000X mZ/zpstMlMuPDFsqUOBa7gEjbptea2PemLI8zP0nR+qwP4WqViie8BH4qQslihA6 d1j7x52PPEByU5hq7fFE7sY/RdqN59jAZi1LpcXXU693KDLk0z8rcXXQIaE1ZD0x fH0Nf5KB7iToYH/Sn7hwPGKQnRqLubrFtxf+mTXLmlJI/53ft+2sMcuaEuiCckMd 8mBLx4478yM= =qxsv -END PGP SIGNATURE- --- End Message --- --- Begin Message --- On Sun, 2019-08-18 at 11:42 +0200, Nicolas Braud-Santoni wrote: > nmu lutok_0.4+dfsg-1 . all amd64 . unstable . -m "Rebuild on buildd > for transition to bullseye" > Unfortunately arch:all packages are not currently usefully binNMUable, so this will need a source upload. Regards, Adam--- End Message ---
Bug#933764: buster-pu: package e2fsprogs/1.44.5-1+deb10u1
Control: tag -1 - d-i Hi Jonathan, On Sun, Aug 04, 2019 at 02:37:25PM +0100, Jonathan Wiltshire wrote: > As there's a udeb involved I will just check with the d-i release managers > that this isn't an issue, though I can't see that fixing a crash would be > all that controversial. I can confirm that d-i doesn't call e4defrag. (The binary isn't even installed in the udeb) Best, nicoo, for the d-i team signature.asc Description: PGP signature
Processed: Re: Bug#933764: buster-pu: package e2fsprogs/1.44.5-1+deb10u1
Processing control commands: > tag -1 - d-i Bug #933764 [release.debian.org] buster-pu: package e2fsprogs/1.44.5-1+deb10u1 Removed tag(s) d-i. -- 933764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933764 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#935028: nmu: lutok_0.4+dfsg-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 nmu lutok_0.4+dfsg-1 . all amd64 . unstable . -m "Rebuild on buildd for transition to bullseye" - -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEU7EqA8ZVHYoLJhPE5vmO4pLV7MsFAl1ZHWcRHG5pY29vQGRl Ymlhbi5vcmcACgkQ5vmO4pLV7Mtb0A//R48O/DONlsLBGW4ZyelG+WnO8RTtf9oV CScKgbfvSQGfQjbVucnLtgff22QexedUdkkNOIEaWSsqNvvhXFU+VFbTv2YwyHFI Bc2l0eGHy9YzxJhUppdiNQvyzwO2RNS8b1htcQp7HVCJ9knzrldA4mUhlmGUfSbY SVVI6/efAvCniyRePvQxsE10ugbMQwAkhbkf0zRixtC+5jv7NkK2rcVPQZqOlmG8 w6ZjElU90wbpf/ZHcE1MftTBPkERyN5OlvWAhMBxYaTzCTZZRSFpcds/DscWMQXp EWwyg1Xa6MSHfz9MJUT57qKtu95we6yRmzzLeC0wrC5RrDEHTayurTM+e+UZEsA0 D2idzZTvvWZxYGmvBoRTUj8BFGmJD5QWKMVmqHwdOSd7GIhJoTmflDB6Pv17le1I cCKv+IJ0wJDef8ls8DnHjHZ5saBzmZtQRZH8JD9Aj7/rP9epGiNQ0fEuJ6oR000X mZ/zpstMlMuPDFsqUOBa7gEjbptea2PemLI8zP0nR+qwP4WqViie8BH4qQslihA6 d1j7x52PPEByU5hq7fFE7sY/RdqN59jAZi1LpcXXU693KDLk0z8rcXXQIaE1ZD0x fH0Nf5KB7iToYH/Sn7hwPGKQnRqLubrFtxf+mTXLmlJI/53ft+2sMcuaEuiCckMd 8mBLx4478yM= =qxsv -END PGP SIGNATURE-
Re: Bits from the Release Team: ride like the wind, Bullseye!
Lisandro Damián Nicanor Pérez Meyer writes ("Re: Bits from the Release Team:
ride like the wind, Bullseye!"):
> My personal point of view (and because of this it might be biased)
> is that the maintainers of the packages that ship autopkgtest should
> be the reponsibles for any breackage it might occur on them because:
>
> - They added autopkgtests, so they are showing an intent on
> reviewing them when they fail.
> - They will certainly know their packages better than the library
> maintainer, and thus they have more chances to get the root of the
> issue sooner. Of course that might mean finding a bug in the
> library, but that's just ok.
In the general case the proper investigation of a bug might need
involvement from both people, collaboratively. That involves a kind
of ping pong on a technical level.
> On 19/08/08 09:46, Paul Gevers wrote:
> > I think we should also try to improve the visibility towards reverse
> > dependencies that their autopkgtest is blocking other packages. I would
> > love tracker (and the old pts) to show this on their page. (Working on
> > such a patch is on my TODO list, except not at the top).
I already made grep-excuses print this information. It has been very
helpful to me. Maybe we should make --autopkgtests the default ?
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
