| 2024-02-21 00:18:07 |
Vladimir Petko |
bug |
|
|
added bug |
| 2024-02-21 00:18:14 |
Vladimir Petko |
byte-buddy (Ubuntu): assignee |
|
Vladimir Petko (vpa1977) |
|
| 2024-02-21 00:18:42 |
Vladimir Petko |
description |
Current uploaded version has a repack suffix `~us`
debian/libbyte-buddy-java.poms have --has-package-version switch that indicates that POM version exactly matches Debian version.
This causes all dependencies generate Depends: libbyte-buddy-java (>= 1.14.1) instead of (>= 1.14.1~),
making the dependency uninstallable after rebuild. |
Current uploaded version has a repack suffix `~us`
debian/libbyte-buddy-java.poms have --has-package-version switch that indicates that POM version exactly matches Debian version.
This causes all dependencies generate Depends: libbyte-buddy-java (>= 1.14.1) instead of (>= 1.14.1~) when building,
making the dependency uninstallable after rebuild. |
|
| 2024-02-21 00:18:53 |
Vladimir Petko |
tags |
|
ftbfs |
|
| 2024-02-21 00:23:16 |
Vladimir Petko |
description |
Current uploaded version has a repack suffix `~us`
debian/libbyte-buddy-java.poms have --has-package-version switch that indicates that POM version exactly matches Debian version.
This causes all dependencies generate Depends: libbyte-buddy-java (>= 1.14.1) instead of (>= 1.14.1~) when building,
making the dependency uninstallable after rebuild. |
Current uploaded version has a repack suffix `~us`
debian/libbyte-buddy-java.poms have --has-package-version switch that indicates that POM version exactly matches Debian version.
This causes all dependencies generate Depends: libbyte-buddy-java (>= 1.14.1) instead of (>= 1.14.1~) when building,
making the dependency uninstallable after rebuild.
Reverse-Depends:
* easymock
* mockito
* perfmark-java |
|
| 2024-02-21 00:23:51 |
Vladimir Petko |
description |
Current uploaded version has a repack suffix `~us`
debian/libbyte-buddy-java.poms have --has-package-version switch that indicates that POM version exactly matches Debian version.
This causes all dependencies generate Depends: libbyte-buddy-java (>= 1.14.1) instead of (>= 1.14.1~) when building,
making the dependency uninstallable after rebuild.
Reverse-Depends:
* easymock
* mockito
* perfmark-java |
Current uploaded version has a repack suffix `~us`
debian/libbyte-buddy-java.poms have --has-package-version switch that indicates that POM version exactly matches Debian version.
This causes all dependencies generate Depends: libbyte-buddy-java (>= 1.14.1) instead of (>= 1.14.1~) in {maven:Depends} variable of the control file, making the dependency uninstallable after rebuild.
Reverse-Depends:
* easymock
* mockito
* perfmark-java |
|
| 2024-02-21 00:25:54 |
Vladimir Petko |
description |
Current uploaded version has a repack suffix `~us`
debian/libbyte-buddy-java.poms have --has-package-version switch that indicates that POM version exactly matches Debian version.
This causes all dependencies generate Depends: libbyte-buddy-java (>= 1.14.1) instead of (>= 1.14.1~) in {maven:Depends} variable of the control file, making the dependency uninstallable after rebuild.
Reverse-Depends:
* easymock
* mockito
* perfmark-java |
Current uploaded version has a repack suffix `~us`
debian/libbyte-buddy-java.poms have --has-package-version switch that indicates that POM version exactly matches Debian version.
This causes all dependencies generate Depends: libbyte-buddy-java (>= 1.14.1) instead of (>= 1.14.1~) in {maven:Depends} variable of the control file, making the dependency uninstallable after rebuild.
Reverse-Depends:
* easymock
* mockito
* perfmark-java
The issue happened because reverse dependencies were rebuilt, but not tested for instability after rebuild. |
|
| 2024-02-21 01:31:25 |
Vladimir Petko |
merge proposal linked |
|
https://code.launchpad.net/~vpa1977/ubuntu/+source/easymock/+git/easymock/+merge/460890 |
|
| 2024-02-21 01:49:36 |
Vladimir Petko |
merge proposal linked |
|
https://code.launchpad.net/~vpa1977/ubuntu/+source/byte-buddy/+git/byte-buddy/+merge/460891 |
|
| 2024-02-21 01:50:51 |
Vladimir Petko |
description |
Current uploaded version has a repack suffix `~us`
debian/libbyte-buddy-java.poms have --has-package-version switch that indicates that POM version exactly matches Debian version.
This causes all dependencies generate Depends: libbyte-buddy-java (>= 1.14.1) instead of (>= 1.14.1~) in {maven:Depends} variable of the control file, making the dependency uninstallable after rebuild.
Reverse-Depends:
* easymock
* mockito
* perfmark-java
The issue happened because reverse dependencies were rebuilt, but not tested for instability after rebuild. |
Current uploaded version has a repack suffix `~us`
debian/libbyte-buddy-java.poms have --has-package-version switch that indicates that POM version exactly matches Debian version.
This causes all dependencies generate Depends: libbyte-buddy-java (>= 1.14.1) instead of (>= 1.14.1~) in {maven:Depends} variable of the control file, making the dependency uninstallable after rebuild.
Packages dependant on libbyte-buddy-java currently in the archive:
Package: libeasymock-java
Depends: libasm-java (>= 9.4), libbyte-buddy-java (>= 1.12.23), libobjenesis-java (>= 3.3)
Package: libassertj-core-java
Depends: libbyte-buddy-java (>= 1.8.2)
Package: libjmock2-java
Depends: libasm-java (>= 9.0), libbsh-java (>= 2.0b4), libbyte-buddy-java (>= 1.8.2), libcglib-java (>= 3.2.12), libfindbugs-annotations-java, libhamcrest-java, libobjenesis-java (>= 3.1)
Package: libmockito-java
Depends: libhamcrest-java, libbyte-buddy-java (>= 1.8.2-2~), libobjenesis-java
So we do not need to upload no change rebuilds for them.
The issue happened because reverse dependencies were rebuilt, but not tested for instability after rebuild. |
|
| 2024-02-21 01:58:32 |
Vladimir Petko |
summary |
easymock is uninstallable due to --has-package-version switch in byte-buddy |
easymock is uninstallable after rebuild due to --has-package-version switch in byte-buddy |
|
| 2024-02-21 02:04:28 |
Vladimir Petko |
attachment added |
|
piuparts-byte-buddy.log.gz https://bugs.launchpad.net/ubuntu/+source/byte-buddy/+bug/2054488/+attachment/5747894/+files/piuparts-byte-buddy.log.gz |
|
| 2024-02-21 04:59:52 |
Vladimir Petko |
description |
Current uploaded version has a repack suffix `~us`
debian/libbyte-buddy-java.poms have --has-package-version switch that indicates that POM version exactly matches Debian version.
This causes all dependencies generate Depends: libbyte-buddy-java (>= 1.14.1) instead of (>= 1.14.1~) in {maven:Depends} variable of the control file, making the dependency uninstallable after rebuild.
Packages dependant on libbyte-buddy-java currently in the archive:
Package: libeasymock-java
Depends: libasm-java (>= 9.4), libbyte-buddy-java (>= 1.12.23), libobjenesis-java (>= 3.3)
Package: libassertj-core-java
Depends: libbyte-buddy-java (>= 1.8.2)
Package: libjmock2-java
Depends: libasm-java (>= 9.0), libbsh-java (>= 2.0b4), libbyte-buddy-java (>= 1.8.2), libcglib-java (>= 3.2.12), libfindbugs-annotations-java, libhamcrest-java, libobjenesis-java (>= 3.1)
Package: libmockito-java
Depends: libhamcrest-java, libbyte-buddy-java (>= 1.8.2-2~), libobjenesis-java
So we do not need to upload no change rebuilds for them.
The issue happened because reverse dependencies were rebuilt, but not tested for instability after rebuild. |
Current uploaded version has a repack suffix `~us`
debian/libbyte-buddy-java.poms have --has-package-version switch that indicates that POM version exactly matches Debian version.
This causes all dependencies generate Depends: libbyte-buddy-java (>= 1.14.1) instead of (>= 1.14.1~) in {maven:Depends} variable of the control file, making the dependency uninstallable after rebuild.
Removing --has-package-version will generate an unversioned dependency and can be used as a workaround until --has-package-version flag supports Debian repack syntax.
Packages dependant on libbyte-buddy-java currently in the archive:
Package: libeasymock-java
Depends: libasm-java (>= 9.4), libbyte-buddy-java (>= 1.12.23), libobjenesis-java (>= 3.3)
Package: libassertj-core-java
Depends: libbyte-buddy-java (>= 1.8.2)
Package: libjmock2-java
Depends: libasm-java (>= 9.0), libbsh-java (>= 2.0b4), libbyte-buddy-java (>= 1.8.2), libcglib-java (>= 3.2.12), libfindbugs-annotations-java, libhamcrest-java, libobjenesis-java (>= 3.1)
Package: libmockito-java
Depends: libhamcrest-java, libbyte-buddy-java (>= 1.8.2-2~), libobjenesis-java
So we do not need to upload no change rebuilds for them.
The issue happened because reverse dependencies were rebuilt, but not tested for instability after rebuild. |
|
| 2024-02-21 06:59:39 |
Vladimir Petko |
attachment added |
|
piuparts-byte-buddy.log.gz https://bugs.launchpad.net/ubuntu/+source/byte-buddy/+bug/2054488/+attachment/5747991/+files/piuparts-byte-buddy.log.gz |
|
| 2024-02-21 07:00:19 |
Vladimir Petko |
description |
Current uploaded version has a repack suffix `~us`
debian/libbyte-buddy-java.poms have --has-package-version switch that indicates that POM version exactly matches Debian version.
This causes all dependencies generate Depends: libbyte-buddy-java (>= 1.14.1) instead of (>= 1.14.1~) in {maven:Depends} variable of the control file, making the dependency uninstallable after rebuild.
Removing --has-package-version will generate an unversioned dependency and can be used as a workaround until --has-package-version flag supports Debian repack syntax.
Packages dependant on libbyte-buddy-java currently in the archive:
Package: libeasymock-java
Depends: libasm-java (>= 9.4), libbyte-buddy-java (>= 1.12.23), libobjenesis-java (>= 3.3)
Package: libassertj-core-java
Depends: libbyte-buddy-java (>= 1.8.2)
Package: libjmock2-java
Depends: libasm-java (>= 9.0), libbsh-java (>= 2.0b4), libbyte-buddy-java (>= 1.8.2), libcglib-java (>= 3.2.12), libfindbugs-annotations-java, libhamcrest-java, libobjenesis-java (>= 3.1)
Package: libmockito-java
Depends: libhamcrest-java, libbyte-buddy-java (>= 1.8.2-2~), libobjenesis-java
So we do not need to upload no change rebuilds for them.
The issue happened because reverse dependencies were rebuilt, but not tested for instability after rebuild. |
Current uploaded version has a repack suffix `~us`
debian/libbyte-buddy-java.poms have --has-package-version switch that indicates that POM version exactly matches Debian version.
This causes all dependencies generate Depends: libbyte-buddy-java (>= 1.14.1) instead of (>= 1.14.1~) in {maven:Depends} variable of the control file, making the dependency uninstallable after rebuild.
Removing --has-package-version will generate an unversioned dependency. We can workaround the issue by manually replacing pom version with the version containing the repack suffix.
Packages dependant on libbyte-buddy-java currently in the archive:
Package: libeasymock-java
Depends: libasm-java (>= 9.4), libbyte-buddy-java (>= 1.12.23), libobjenesis-java (>= 3.3)
Package: libassertj-core-java
Depends: libbyte-buddy-java (>= 1.8.2)
Package: libjmock2-java
Depends: libasm-java (>= 9.0), libbsh-java (>= 2.0b4), libbyte-buddy-java (>= 1.8.2), libcglib-java (>= 3.2.12), libfindbugs-annotations-java, libhamcrest-java, libobjenesis-java (>= 3.1)
Package: libmockito-java
Depends: libhamcrest-java, libbyte-buddy-java (>= 1.8.2-2~), libobjenesis-java
So we do not need to upload no change rebuilds for them.
The issue happened because reverse dependencies were rebuilt, but not tested for instability after rebuild. |
|
| 2024-02-22 01:28:52 |
Launchpad Janitor |
byte-buddy (Ubuntu): status |
New |
Fix Released |
|
