Bug#980644: [Android-tools-devel] Bug#980644: android-sdk-platform-tools-common: no Multi-Arch annotation prevents adb upgrade
Thorsten Glaser: Hans-Christoph Steiner dixit: Right now, we can only commit to supporting the arches that upstream supports (amd64 and arm64), so I'm downgrading the severity. It’d be the same if you’d install either of these, it’s *not* an architecture-specific problem. I could never wrap my head around the Multi-Arch: stuff. Please consider doing so in the near future. Helmut Grohne can help if you have concrete questions as well. This is becoming more and more important. I have tried in the past. I have way too much going to spend more time on it. That's why we have team packages, so each person does not need to know all the details. Thanks for your contribution! I would accept a merge request on salsa for this, if it passes in gitlab-ci. It’s a one-liner that changes package metadata only, so it’s got no chance not to pass. I tested it locally yesterday already, so I’ll try to wrap my head around this Salsa thing and give you one. Thanks for taking the time to learn more about salsa! I think the salsa/gitlab workflow will really improve Debian because it is a very common workflow in software development, and it is built around making it easy for anyone to contribute. Having the build and CI integrated into the workflow is a really a bit win over having to upload to ftp-master to see the results. .hc
Bug#980644: [Android-tools-devel] Bug#980644: android-sdk-platform-tools-common: no Multi-Arch annotation prevents adb upgrade
Dixi quod… >Hans-Christoph Steiner dixit: > >> I would accept a >> merge request on salsa for this, if it passes in gitlab-ci. > >It’s a one-liner that changes package metadata only, so it’s OK, it became three lines because the other two arch:all packages also qualify for M-A:foreign. https://salsa.debian.org/android-tools-team/android-sdk-meta/-/merge_requests/6 bye, //mirabilos -- you introduced a merge commit│ % g rebase -i HEAD^^ sorry, no idea and rebasing just fscked │ Segmentation should have cloned into a clean repo │ fault (core dumped) if I rebase that now, it's really ugh │ wuahh
Bug#980644: [Android-tools-devel] Bug#980644: android-sdk-platform-tools-common: no Multi-Arch annotation prevents adb upgrade
Hans-Christoph Steiner dixit: > Right now, we can only commit to supporting the arches that upstream supports > (amd64 and arm64), so I'm downgrading the severity. It’d be the same if you’d install either of these, it’s *not* an architecture-specific problem. > I could never wrap my head around the Multi-Arch: stuff. Please consider doing so in the near future. Helmut Grohne can help if you have concrete questions as well. This is becoming more and more important. > I would accept a > merge request on salsa for this, if it passes in gitlab-ci. It’s a one-liner that changes package metadata only, so it’s got no chance not to pass. I tested it locally yesterday already, so I’ll try to wrap my head around this Salsa thing and give you one. Thanks, //mirabilos -- >> Why don't you use JavaScript? I also don't like enabling JavaScript in > Because I use lynx as browser. +1 -- Octavio Alvarez, me and ⡍⠁⠗⠊⠕ (Mario Lang) on debian-devel
Bug#980644: [Android-tools-devel] Bug#980644: android-sdk-platform-tools-common: no Multi-Arch annotation prevents adb upgrade
Control: severity -1 normal Right now, we can only commit to supporting the arches that upstream supports (amd64 and arm64), so I'm downgrading the severity. I could never wrap my head around the Multi-Arch: stuff. I would accept a merge request on salsa for this, if it passes in gitlab-ci.
