Activity log for bug #2071468

Date Who What changed Old value New value Message
2024-06-28 12:58:31 Benjamin Drung bug added bug
2024-06-28 13:01:03 Benjamin Drung description The ELF package note metadata introduced in dpkg 1.22.6ubuntu11 (refined in 1.22.6ubuntu14) can cause this failure: ``` gcc fatal error: environment variable ‘DEB_HOST_ARCH’ not defined ``` This happens when the -spec parameter is set but the needed environment variables are not set. Cases: 1. Only the LDFLAGS is queried from dpkg-buildflags. Affected source packages builds: python3.12, openjdk-21, cdbs (causing dvbstreamer and rp-pppoe fail to build) 2. autopkgtests The ELF package note metadata introduced in dpkg 1.22.6ubuntu11 (refined in 1.22.6ubuntu14) can cause this failure: ``` gcc fatal error: environment variable ‘DEB_HOST_ARCH’ not defined ``` This happens when the `-specs=/usr/share/dpkg/elf-package-metadata.specs` parameter is set but the needed environment variables are not set. Cases: 1. Only the LDFLAGS is queried from dpkg-buildflags. Affected source packages builds: python3.12, openjdk-21, cdbs (causing dvbstreamer and rp-pppoe fail to build) 2. autopkgtests
2024-06-28 13:03:34 Benjamin Drung summary ELF package metadata failures ELF package metadata failure: environment variable ‘DEB_HOST_ARCH’ not defined
2024-06-28 21:35:36 Benjamin Drung description The ELF package note metadata introduced in dpkg 1.22.6ubuntu11 (refined in 1.22.6ubuntu14) can cause this failure: ``` gcc fatal error: environment variable ‘DEB_HOST_ARCH’ not defined ``` This happens when the `-specs=/usr/share/dpkg/elf-package-metadata.specs` parameter is set but the needed environment variables are not set. Cases: 1. Only the LDFLAGS is queried from dpkg-buildflags. Affected source packages builds: python3.12, openjdk-21, cdbs (causing dvbstreamer and rp-pppoe fail to build) 2. autopkgtests The ELF package note metadata introduced in dpkg 1.22.6ubuntu11 (refined in 1.22.6ubuntu14) can cause this failure: ``` gcc fatal error: environment variable ‘DEB_HOST_ARCH’ not defined ``` This happens when the `-specs=/usr/share/dpkg/elf-package-metadata.specs` parameter is set but the needed environment variables are not set. Cases: 1. Only the LDFLAGS is queried from dpkg-buildflags. Affected source packages builds: python3.12, openjdk-21, cdbs (causing dvbstreamer and rp-pppoe fail to build) 2. autopkgtests This approach is too fragile. An alternative approach is specify the `--package-metadata` linker flag directly. The problem with that approach is that the curly brackets and quotation marks need to be escaped. Example failure: Building dpkg would add this parameter to the LDFLAGS: ``` -Wl,--package-metadata,{"type":"deb","os":"ubuntu","name":"dpkg","version":"1.22.6ubuntu15","architecture":"amd64"} ``` The following configure script call (non-relevant parameters deleted): ``` $ gcc -Wl,--package-metadata,{type:deb,os:ubuntu,name:dpkg,version:1.22.6ubuntu15,architecture:amd64} /usr/bin/ld: cannot find {type:deb: No such file or directory /usr/bin/ld: cannot find os:ubuntu: No such file or directory /usr/bin/ld: cannot find name:dpkg: No such file or directory /usr/bin/ld: cannot find version:1.22.6ubuntu15: No such file or directory /usr/bin/ld: cannot find architecture:amd64}: No such file or directory ``` Proposed solution: Add support for an `--escaped-package-metadata` parameter that takes an URL encoded (RFC 3986) parameter. Example: ``` -Wl,--encoded-package-metadata,%7B%22type%22:%22deb%22%2C%22os%22:%22ubuntu%22%2C%22name%22:%22dpkg%22%2C%22version%22:%221.22.6ubuntu15%22%2C%22architecture%22:%22amd64%22%7D ```
2024-06-28 21:39:27 Benjamin Drung description The ELF package note metadata introduced in dpkg 1.22.6ubuntu11 (refined in 1.22.6ubuntu14) can cause this failure: ``` gcc fatal error: environment variable ‘DEB_HOST_ARCH’ not defined ``` This happens when the `-specs=/usr/share/dpkg/elf-package-metadata.specs` parameter is set but the needed environment variables are not set. Cases: 1. Only the LDFLAGS is queried from dpkg-buildflags. Affected source packages builds: python3.12, openjdk-21, cdbs (causing dvbstreamer and rp-pppoe fail to build) 2. autopkgtests This approach is too fragile. An alternative approach is specify the `--package-metadata` linker flag directly. The problem with that approach is that the curly brackets and quotation marks need to be escaped. Example failure: Building dpkg would add this parameter to the LDFLAGS: ``` -Wl,--package-metadata,{"type":"deb","os":"ubuntu","name":"dpkg","version":"1.22.6ubuntu15","architecture":"amd64"} ``` The following configure script call (non-relevant parameters deleted): ``` $ gcc -Wl,--package-metadata,{type:deb,os:ubuntu,name:dpkg,version:1.22.6ubuntu15,architecture:amd64} /usr/bin/ld: cannot find {type:deb: No such file or directory /usr/bin/ld: cannot find os:ubuntu: No such file or directory /usr/bin/ld: cannot find name:dpkg: No such file or directory /usr/bin/ld: cannot find version:1.22.6ubuntu15: No such file or directory /usr/bin/ld: cannot find architecture:amd64}: No such file or directory ``` Proposed solution: Add support for an `--escaped-package-metadata` parameter that takes an URL encoded (RFC 3986) parameter. Example: ``` -Wl,--encoded-package-metadata,%7B%22type%22:%22deb%22%2C%22os%22:%22ubuntu%22%2C%22name%22:%22dpkg%22%2C%22version%22:%221.22.6ubuntu15%22%2C%22architecture%22:%22amd64%22%7D ``` The ELF package note metadata introduced in dpkg 1.22.6ubuntu11 (refined in 1.22.6ubuntu14) can cause this failure: ``` gcc fatal error: environment variable ‘DEB_HOST_ARCH’ not defined ``` This happens when the `-specs=/usr/share/dpkg/elf-package-metadata.specs` parameter is set but the needed environment variables are not set. Cases: 1. Only the LDFLAGS is queried from dpkg-buildflags. Affected source packages builds: python3.12, openjdk-21, cdbs (causing dvbstreamer and rp-pppoe fail to build) 2. autopkgtests This approach is too fragile. An alternative approach would be to specify the `--package-metadata` linker flag directly. The problem with that approach is that the curly brackets and quotation marks need to be escaped. Example failure: Building dpkg would add this parameter to the LDFLAGS: ``` -Wl,--package-metadata,{"type":"deb","os":"ubuntu","name":"dpkg","version":"1.22.6ubuntu15","architecture":"amd64"} ``` The following configure script call (non-relevant parameters deleted): ``` $ gcc -Wl,--package-metadata,{type:deb,os:ubuntu,name:dpkg,version:1.22.6ubuntu15,architecture:amd64} /usr/bin/ld: cannot find {type:deb: No such file or directory /usr/bin/ld: cannot find os:ubuntu: No such file or directory /usr/bin/ld: cannot find name:dpkg: No such file or directory /usr/bin/ld: cannot find version:1.22.6ubuntu15: No such file or directory /usr/bin/ld: cannot find architecture:amd64}: No such file or directory ``` Proposed solution: Add support for an `--escaped-package-metadata` parameter to the linkers that takes an URL encoded (RFC 3986) parameter. Example: ``` -Wl,--encoded-package-metadata,%7B%22type%22:%22deb%22%2C%22os%22:%22ubuntu%22%2C%22name%22:%22dpkg%22%2C%22version%22:%221.22.6ubuntu15%22%2C%22architecture%22:%22amd64%22%7D ```
2024-06-29 15:27:46 Luca Boccassi bug added subscriber Luca Boccassi
2024-06-29 17:34:28 Andreas Hasenack tags update-excuse
2024-06-29 17:40:04 Andreas Hasenack bug added subscriber Andreas Hasenack
2024-06-29 22:28:28 Jeremy Bícha bug task added octave (Ubuntu)
2024-06-29 23:00:37 Jeremy Bícha affects octave (Ubuntu) mwrap (Ubuntu)
2024-06-29 23:00:37 Jeremy Bícha mwrap (Ubuntu): status New Fix Committed
2024-06-29 23:00:43 Jeremy Bícha mwrap (Ubuntu): importance Undecided High
2024-06-29 23:13:27 Jeremy Bícha bug task added gsequencer (Ubuntu)
2024-06-29 23:13:36 Jeremy Bícha bug task added mosh (Ubuntu)
2024-06-29 23:13:46 Jeremy Bícha bug task added asymptote (Ubuntu)
2024-06-29 23:13:51 Jeremy Bícha asymptote (Ubuntu): importance Undecided High
2024-06-29 23:13:54 Jeremy Bícha asymptote (Ubuntu): status New Triaged
2024-06-29 23:13:56 Jeremy Bícha dpkg (Ubuntu): importance Undecided High
2024-06-29 23:13:59 Jeremy Bícha dpkg (Ubuntu): status New Triaged
2024-06-29 23:14:03 Jeremy Bícha gsequencer (Ubuntu): importance Undecided High
2024-06-29 23:14:06 Jeremy Bícha gsequencer (Ubuntu): status New Triaged
2024-06-29 23:14:09 Jeremy Bícha mosh (Ubuntu): importance Undecided High
2024-06-29 23:14:11 Jeremy Bícha mosh (Ubuntu): status New Triaged
2024-06-29 23:35:26 Jeremy Bícha mosh (Ubuntu): status Triaged Fix Committed
2024-06-30 00:55:46 Jeremy Bícha asymptote (Ubuntu): status Triaged Fix Committed
2024-06-30 03:37:10 Launchpad Janitor mosh (Ubuntu): status Fix Committed Fix Released
2024-06-30 03:37:11 Launchpad Janitor mwrap (Ubuntu): status Fix Committed Fix Released
2024-06-30 06:45:03 Launchpad Janitor asymptote (Ubuntu): status Fix Committed Fix Released
2024-06-30 19:32:25 Launchpad Janitor gsequencer (Ubuntu): status Triaged Fix Released
2024-06-30 22:08:42 Jeremy Bícha bug added subscriber Jeremy Bícha
2024-07-01 08:07:59 Benjamin Drung description The ELF package note metadata introduced in dpkg 1.22.6ubuntu11 (refined in 1.22.6ubuntu14) can cause this failure: ``` gcc fatal error: environment variable ‘DEB_HOST_ARCH’ not defined ``` This happens when the `-specs=/usr/share/dpkg/elf-package-metadata.specs` parameter is set but the needed environment variables are not set. Cases: 1. Only the LDFLAGS is queried from dpkg-buildflags. Affected source packages builds: python3.12, openjdk-21, cdbs (causing dvbstreamer and rp-pppoe fail to build) 2. autopkgtests This approach is too fragile. An alternative approach would be to specify the `--package-metadata` linker flag directly. The problem with that approach is that the curly brackets and quotation marks need to be escaped. Example failure: Building dpkg would add this parameter to the LDFLAGS: ``` -Wl,--package-metadata,{"type":"deb","os":"ubuntu","name":"dpkg","version":"1.22.6ubuntu15","architecture":"amd64"} ``` The following configure script call (non-relevant parameters deleted): ``` $ gcc -Wl,--package-metadata,{type:deb,os:ubuntu,name:dpkg,version:1.22.6ubuntu15,architecture:amd64} /usr/bin/ld: cannot find {type:deb: No such file or directory /usr/bin/ld: cannot find os:ubuntu: No such file or directory /usr/bin/ld: cannot find name:dpkg: No such file or directory /usr/bin/ld: cannot find version:1.22.6ubuntu15: No such file or directory /usr/bin/ld: cannot find architecture:amd64}: No such file or directory ``` Proposed solution: Add support for an `--escaped-package-metadata` parameter to the linkers that takes an URL encoded (RFC 3986) parameter. Example: ``` -Wl,--encoded-package-metadata,%7B%22type%22:%22deb%22%2C%22os%22:%22ubuntu%22%2C%22name%22:%22dpkg%22%2C%22version%22:%221.22.6ubuntu15%22%2C%22architecture%22:%22amd64%22%7D ``` The ELF package note metadata introduced in dpkg 1.22.6ubuntu11 (refined in 1.22.6ubuntu14) can cause this failure: ``` gcc fatal error: environment variable ‘DEB_HOST_ARCH’ not defined ``` This happens when the `-specs=/usr/share/dpkg/elf-package-metadata.specs` parameter is set but the needed environment variables are not set. Cases: 1. Only the LDFLAGS is queried from dpkg-buildflags. Affected source packages builds: python3.12, openjdk-21, cdbs (causing dvbstreamer and rp-pppoe fail to build) 2. autopkgtests 3. debugging a crash of an application build with the -spec parameter This approach is too fragile. An alternative approach would be to specify the `--package-metadata` linker flag directly. The problem with that approach is that the curly brackets and quotation marks need to be escaped. Example failure: Building dpkg would add this parameter to the LDFLAGS: ``` -Wl,--package-metadata,{"type":"deb","os":"ubuntu","name":"dpkg","version":"1.22.6ubuntu15","architecture":"amd64"} ``` The following configure script call (non-relevant parameters deleted): ``` $ gcc -Wl,--package-metadata,{type:deb,os:ubuntu,name:dpkg,version:1.22.6ubuntu15,architecture:amd64} /usr/bin/ld: cannot find {type:deb: No such file or directory /usr/bin/ld: cannot find os:ubuntu: No such file or directory /usr/bin/ld: cannot find name:dpkg: No such file or directory /usr/bin/ld: cannot find version:1.22.6ubuntu15: No such file or directory /usr/bin/ld: cannot find architecture:amd64}: No such file or directory ``` Proposed solution: Add support for an `--escaped-package-metadata` parameter to the linkers that takes an URL encoded (RFC 3986) parameter. Example: ``` -Wl,--encoded-package-metadata,%7B%22type%22:%22deb%22%2C%22os%22:%22ubuntu%22%2C%22name%22:%22dpkg%22%2C%22version%22:%221.22.6ubuntu15%22%2C%22architecture%22:%22amd64%22%7D ```
2024-07-02 15:37:49 Athos Ribeiro bug task added squid (Ubuntu)
2024-07-02 15:37:58 Athos Ribeiro squid (Ubuntu): status New Triaged
2024-07-02 17:22:18 Launchpad Janitor merge proposal linked https://code.launchpad.net/~athos-ribeiro/ubuntu/+source/squid/+git/squid/+merge/468531
2024-07-02 17:22:54 Athos Ribeiro merge proposal unlinked https://code.launchpad.net/~athos-ribeiro/ubuntu/+source/squid/+git/squid/+merge/468531
2024-07-04 09:11:14 Julian Andres Klode description The ELF package note metadata introduced in dpkg 1.22.6ubuntu11 (refined in 1.22.6ubuntu14) can cause this failure: ``` gcc fatal error: environment variable ‘DEB_HOST_ARCH’ not defined ``` This happens when the `-specs=/usr/share/dpkg/elf-package-metadata.specs` parameter is set but the needed environment variables are not set. Cases: 1. Only the LDFLAGS is queried from dpkg-buildflags. Affected source packages builds: python3.12, openjdk-21, cdbs (causing dvbstreamer and rp-pppoe fail to build) 2. autopkgtests 3. debugging a crash of an application build with the -spec parameter This approach is too fragile. An alternative approach would be to specify the `--package-metadata` linker flag directly. The problem with that approach is that the curly brackets and quotation marks need to be escaped. Example failure: Building dpkg would add this parameter to the LDFLAGS: ``` -Wl,--package-metadata,{"type":"deb","os":"ubuntu","name":"dpkg","version":"1.22.6ubuntu15","architecture":"amd64"} ``` The following configure script call (non-relevant parameters deleted): ``` $ gcc -Wl,--package-metadata,{type:deb,os:ubuntu,name:dpkg,version:1.22.6ubuntu15,architecture:amd64} /usr/bin/ld: cannot find {type:deb: No such file or directory /usr/bin/ld: cannot find os:ubuntu: No such file or directory /usr/bin/ld: cannot find name:dpkg: No such file or directory /usr/bin/ld: cannot find version:1.22.6ubuntu15: No such file or directory /usr/bin/ld: cannot find architecture:amd64}: No such file or directory ``` Proposed solution: Add support for an `--escaped-package-metadata` parameter to the linkers that takes an URL encoded (RFC 3986) parameter. Example: ``` -Wl,--encoded-package-metadata,%7B%22type%22:%22deb%22%2C%22os%22:%22ubuntu%22%2C%22name%22:%22dpkg%22%2C%22version%22:%221.22.6ubuntu15%22%2C%22architecture%22:%22amd64%22%7D ``` The ELF package note metadata introduced in dpkg 1.22.6ubuntu11 (refined in 1.22.6ubuntu14) can cause this failure: ``` gcc fatal error: environment variable ‘DEB_HOST_ARCH’ not defined ``` This happens when the `-specs=/usr/share/dpkg/elf-package-metadata.specs` parameter is set but the needed environment variables are not set. Cases: 1. Only the LDFLAGS is queried from dpkg-buildflags. Affected source packages builds: python3.12, openjdk-21, cdbs (causing dvbstreamer and rp-pppoe fail to build) 2. autopkgtests 3. debugging a crash of an application build with the -spec parameter This approach is too fragile. An alternative approach would be to specify the `--package-metadata` linker flag directly. The problem with that approach is that the curly brackets and quotation marks need to be escaped. Example failure: Building dpkg would add this parameter to the LDFLAGS: ``` -Wl,--package-metadata,{"type":"deb","os":"ubuntu","name":"dpkg","version":"1.22.6ubuntu15","architecture":"amd64"} ``` The following configure script call (non-relevant parameters deleted): ``` $ gcc -Wl,--package-metadata,{type:deb,os:ubuntu,name:dpkg,version:1.22.6ubuntu15,architecture:amd64} /usr/bin/ld: cannot find {type:deb: No such file or directory /usr/bin/ld: cannot find os:ubuntu: No such file or directory /usr/bin/ld: cannot find name:dpkg: No such file or directory /usr/bin/ld: cannot find version:1.22.6ubuntu15: No such file or directory /usr/bin/ld: cannot find architecture:amd64}: No such file or directory ``` 4. People like to iteratively continue building the software in the build dir while hacking on the package and then have no environment variable set. Proposed solution: Add support for an `--escaped-package-metadata` parameter to the linkers that takes an URL encoded (RFC 3986) parameter. Example: ``` -Wl,--encoded-package-metadata,%7B%22type%22:%22deb%22%2C%22os%22:%22ubuntu%22%2C%22name%22:%22dpkg%22%2C%22version%22:%221.22.6ubuntu15%22%2C%22architecture%22:%22amd64%22%7D ```
2024-07-04 09:11:45 Benjamin Drung description The ELF package note metadata introduced in dpkg 1.22.6ubuntu11 (refined in 1.22.6ubuntu14) can cause this failure: ``` gcc fatal error: environment variable ‘DEB_HOST_ARCH’ not defined ``` This happens when the `-specs=/usr/share/dpkg/elf-package-metadata.specs` parameter is set but the needed environment variables are not set. Cases: 1. Only the LDFLAGS is queried from dpkg-buildflags. Affected source packages builds: python3.12, openjdk-21, cdbs (causing dvbstreamer and rp-pppoe fail to build) 2. autopkgtests 3. debugging a crash of an application build with the -spec parameter This approach is too fragile. An alternative approach would be to specify the `--package-metadata` linker flag directly. The problem with that approach is that the curly brackets and quotation marks need to be escaped. Example failure: Building dpkg would add this parameter to the LDFLAGS: ``` -Wl,--package-metadata,{"type":"deb","os":"ubuntu","name":"dpkg","version":"1.22.6ubuntu15","architecture":"amd64"} ``` The following configure script call (non-relevant parameters deleted): ``` $ gcc -Wl,--package-metadata,{type:deb,os:ubuntu,name:dpkg,version:1.22.6ubuntu15,architecture:amd64} /usr/bin/ld: cannot find {type:deb: No such file or directory /usr/bin/ld: cannot find os:ubuntu: No such file or directory /usr/bin/ld: cannot find name:dpkg: No such file or directory /usr/bin/ld: cannot find version:1.22.6ubuntu15: No such file or directory /usr/bin/ld: cannot find architecture:amd64}: No such file or directory ``` 4. People like to iteratively continue building the software in the build dir while hacking on the package and then have no environment variable set. Proposed solution: Add support for an `--escaped-package-metadata` parameter to the linkers that takes an URL encoded (RFC 3986) parameter. Example: ``` -Wl,--encoded-package-metadata,%7B%22type%22:%22deb%22%2C%22os%22:%22ubuntu%22%2C%22name%22:%22dpkg%22%2C%22version%22:%221.22.6ubuntu15%22%2C%22architecture%22:%22amd64%22%7D ``` The ELF package note metadata introduced in dpkg 1.22.6ubuntu11 (refined in 1.22.6ubuntu14) can cause this failure: ``` gcc fatal error: environment variable ‘DEB_HOST_ARCH’ not defined ``` This happens when the `-specs=/usr/share/dpkg/elf-package-metadata.specs` parameter is set but the needed environment variables are not set. Cases: 1. Only the LDFLAGS is queried from dpkg-buildflags. Affected source packages builds: python3.12, openjdk-21, cdbs (causing dvbstreamer and rp-pppoe fail to build) 2. autopkgtests 3. debugging a crash of an application build with the -spec parameter 4. People like to iteratively continue building the software in the build dir while hacking on the package and then have no environment variable set. This approach is too fragile. An alternative approach would be to specify the `--package-metadata` linker flag directly. The problem with that approach is that the curly brackets and quotation marks need to be escaped. Example failure: Building dpkg would add this parameter to the LDFLAGS: ``` -Wl,--package-metadata,{"type":"deb","os":"ubuntu","name":"dpkg","version":"1.22.6ubuntu15","architecture":"amd64"} ``` The following configure script call (non-relevant parameters deleted): ``` $ gcc -Wl,--package-metadata,{type:deb,os:ubuntu,name:dpkg,version:1.22.6ubuntu15,architecture:amd64} /usr/bin/ld: cannot find {type:deb: No such file or directory /usr/bin/ld: cannot find os:ubuntu: No such file or directory /usr/bin/ld: cannot find name:dpkg: No such file or directory /usr/bin/ld: cannot find version:1.22.6ubuntu15: No such file or directory /usr/bin/ld: cannot find architecture:amd64}: No such file or directory ``` Proposed solution: Add support for an `--escaped-package-metadata` parameter to the linkers that takes an URL encoded (RFC 3986) parameter. Example: ``` -Wl,--encoded-package-metadata,%7B%22type%22:%22deb%22%2C%22os%22:%22ubuntu%22%2C%22name%22:%22dpkg%22%2C%22version%22:%221.22.6ubuntu15%22%2C%22architecture%22:%22amd64%22%7D ```
2024-07-04 21:31:34 Vladimir Petko bug task added libreoffice (Ubuntu)
2024-07-05 12:18:10 Jeremy Bícha bug task added serf (Ubuntu)
2024-07-05 12:18:17 Jeremy Bícha serf (Ubuntu): importance Undecided High
2024-07-05 12:18:20 Jeremy Bícha serf (Ubuntu): status New Triaged
2024-07-05 12:18:28 Jeremy Bícha tags update-excuse ftbfs oracular update-excuse
2024-07-05 15:37:57 Jeremy Bícha bug task added texinfo (Ubuntu)
2024-07-05 15:38:05 Jeremy Bícha texinfo (Ubuntu): importance Undecided High
2024-07-05 15:38:09 Jeremy Bícha texinfo (Ubuntu): status New Triaged
2024-07-05 15:38:13 Jeremy Bícha squid (Ubuntu): importance Undecided High
2024-07-06 02:07:59 Launchpad Janitor squid (Ubuntu): status Triaged Fix Released
2024-07-06 02:07:59 Launchpad Janitor cve linked 2024-25111
2024-07-06 16:06:39 Jeremy Bícha libreoffice (Ubuntu): status New Fix Released
2024-07-08 20:16:58 Sergio Durigan Junior bug task added curl (Ubuntu)
2024-07-08 20:17:05 Sergio Durigan Junior curl (Ubuntu): status New Triaged
2024-07-08 20:18:51 Sergio Durigan Junior bug task added proftpd-dfsg (Ubuntu)
2024-07-08 20:19:00 Sergio Durigan Junior proftpd-dfsg (Ubuntu): status New Triaged
2024-07-08 20:19:21 Sergio Durigan Junior bug added subscriber Sergio Durigan Junior
2024-07-08 20:19:39 Sergio Durigan Junior curl (Ubuntu): importance Undecided High
2024-07-08 20:19:47 Sergio Durigan Junior proftpd-dfsg (Ubuntu): importance Undecided High
2024-07-08 23:55:56 Launchpad Janitor proftpd-dfsg (Ubuntu): status Triaged Fix Released
2024-07-09 08:16:34 Adrien Nader bug task added jose (Ubuntu)
2024-07-09 08:16:58 Adrien Nader bug task added libtpms (Ubuntu)
2024-07-09 08:18:38 Adrien Nader bug task added proftpd (Ubuntu)
2024-07-09 08:18:50 Adrien Nader bug task added swtpm (Ubuntu)
2024-07-09 14:47:40 Launchpad Janitor swtpm (Ubuntu): status New Fix Released
2024-07-09 16:12:32 Gianfranco Costamagna bug task added haskell-devscripts (Ubuntu)
2024-07-09 17:56:34 Launchpad Janitor haskell-devscripts (Ubuntu): status New Fix Released
2024-07-09 21:59:08 Launchpad Janitor serf (Ubuntu): status Triaged Fix Released
2024-07-10 06:06:59 Dominik Stadler bug added subscriber Dominik Stadler
2024-07-10 14:23:27 Launchpad Janitor curl (Ubuntu): status Triaged Fix Released
2024-07-10 20:19:32 Jeremy Bícha bug task added graphite2 (Ubuntu)
2024-07-10 20:19:42 Jeremy Bícha graphite2 (Ubuntu): importance Undecided High
2024-07-10 20:19:42 Jeremy Bícha graphite2 (Ubuntu): status New Fix Released
2024-07-11 13:34:37 Nathan Teodosio bug task added speech-dispatcher (Ubuntu)
2024-07-11 13:41:10 Nathan Teodosio attachment added Patch for speech-dispatcher 0.12.0~rc2-2 https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/2071468/+attachment/5796206/+files/speechdd.diff
2024-07-11 14:01:55 Nathan Teodosio bug added subscriber Ubuntu Sponsors