Hi all,
yesterday I uploaded dvisvgm_2.13-1 to the archive. For any unknown
reason I deleted the changelog entry for version 2.12-4 from the
d/changelog file, this version is currently in testing. I tried to
cancel the upload using dcut, but this does not work. How to proceed?
- Can we remov
Wookey writes:
> If the package builds on the 32bit arches then I would advise that you
> let it build. We always try to build for all arches in debian and it
> is very annoying if you have say an armhf machine and something is not
> available just because there was some test failure so upstream
On Mon, Jan 24, 2022 at 09:14:08AM +0100, Hilmar Preuße wrote:
> yesterday I uploaded dvisvgm_2.13-1 to the archive. For any unknown reason I
> deleted the changelog entry for version 2.12-4 from the d/changelog file,
> this version is currently in testing. I tried to cancel the upload using
> dcut
On 1/24/22 09:10, Ole Streicher wrote:
> Wookey writes:
>> If the package builds on the 32bit arches then I would advise that you
>> let it build. We always try to build for all arches in debian and it
>> is very annoying if you have say an armhf machine and something is not
>> available just bec
Hi,
Am Mon, Jan 24, 2022 at 10:38:32AM +0100 schrieb Helge Deller:
On 1/24/22 09:10, Ole Streicher wrote:
Wookey writes:
If the package builds on the 32bit arches then I would advise that you
let it build. We always try to build for all arches in debian and it
is very annoying if you have sa
On Mon, Jan 24, 2022 at 09:14:08AM +0100, Hilmar Preuße wrote:
> I tried to cancel the upload using dcut
You can cancel an upload only before it gets processed. This typically
works only for:
* DELAYED uploads
* (if you're lucky) in a short time window after upload
Meow!
--
⢀⣴⠾⠻⢶⣦⠀ Aryans: spl
Helge Deller writes:
> On 1/24/22 09:10, Ole Streicher wrote:
>> Wookey writes:
>>> If the package builds on the 32bit arches then I would advise that you
>>> let it build. We always try to build for all arches in debian and it
>>> is very annoying if you have say an armhf machine and something
On 1/24/22 11:36, Ole Streicher wrote:
> Helge Deller writes:
>> On 1/24/22 09:10, Ole Streicher wrote:
>>> Wookey writes:
If the package builds on the 32bit arches then I would advise that you
let it build. We always try to build for all arches in debian and it
is very annoying i
Hi Helge,
Helge Deller writes:
> That's why I'm saying that you shouldn't exclude by default a *specific*
> architecture. The problem is often not bound to that architecture, but by
> the specifics which define that architecture (endianess, 32/64-bit, ...).
this brings me to the point why we don
Am 24.01.2022 um 09:43 teilte Andrey Rahmatullin mit:
On Mon, Jan 24, 2022 at 09:14:08AM +0100, Hilmar Preuße wrote:
Hi Andrey,
- Can we remove that version 2.13-1 from unstable?
We shouldn't.
And we can't remove it from user machines.
Yes, correct.
- Should I simply upload 2.13-2 and r
10 matches
Mail list logo
