I mean:
In "bt-*" directories there are *.torrent files, but these are unusable
because bittorrent tracker responds "torrent not found" for any torrent
file of Debian 10.12
This is an example:
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/archive/10.12.0-live+non
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
The attached debdiff for golang-github-russellhaering-goxmldsig fixes
CVE-2020-7711 in Buster. This CVE has been marked as no-dsa by the
security team.
Thorsten
golang-gith
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
The attached debdiff for golang-github-russellhaering-goxmldsig fixes
CVE-2020-7711 in Bullseye. This CVE has been marked as no-dsa by the
security team.
Thorsten
diff -Nru go
On 2022-03-28 12:57:38, Paul Gevers wrote:
> Right, multiarch.
> Rebuilding on all architectures wouldn't help, as the other
> architectures would be bumped too, so we only want to rebuild ia64
> and riscv64. Scheduled.
Thanks for the clarifications. I think based on this that in the
future I s
Your message dated Mon, 28 Mar 2022 21:57:38 +0200
with message-id <7b74660b-e7b4-a025-d8d2-868f665af...@debian.org>
and subject line Re: Bug#1008518: nmu: libxxf86vm_1:1.1.4-1+b2
has caused the Debian Bug report #1008518,
regarding nmu: libxxf86vm_1:1.1.4-1+b2
to be marked as done.
This means tha
On 2022-03-28 11:57:14, Paul Gevers wrote:
> Hi Jordan,
>
> On 28-03-2022 10:20, Jordan Justen wrote:
> > nmu libxxf86vm_1:1.1.4-1+b2 . ANY . unstable . -m "riscv64 arch is at
> > 1:1.1.4-1
> > while others are at 1:1.1.4-1+b2"
>
> It may be obvious to you, but, so what? Why is that a problem an
On Mon, Mar 28, 2022 at 04:59:58PM +0200, Jérémy Lal wrote:
>
> Yes, actually all packages depending on libnode-dev/sid now need to depend
> on nodejs/sid, or else autopkgtest runs the tests against nodejs/testing,
> and that fails.
> I'll reupload them if that's all right.
>
> The other solution
Bonjour
Merci de retirer mon adresse mail de votre liste de distribution.
Cordialement
Envoyé depuis Yahoo Mail pour Android
Hi Jordan,
On 28-03-2022 10:20, Jordan Justen wrote:
nmu libxxf86vm_1:1.1.4-1+b2 . ANY . unstable . -m "riscv64 arch is at 1:1.1.4-1
while others are at 1:1.1.4-1+b2"
It may be obvious to you, but, so what? Why is that a problem and how
does rebuilding on all architectures solve that?
Paul
Hi Markus
On Mon, 28 Mar 2022 at 17:30, Markus Blatt wrote:
> I just took a look at the tracker and noticed that opm-common is level 3 and
> opm-simulators is level 2. If build attempts for level 3 come after level 2
> that migth explain the failure in the logs [1] and opm-common should be in a
>
Hi,
I just took a look at the tracker and noticed that opm-common is level 3 and
opm-simulators is level 2. If build attempts for level 3 come after level 2
that migth explain the failure in the logs [1] and opm-common should be in a
level before opm-simulators.
If there is anything that I need
On Mon, Mar 28, 2022 at 4:19 PM Sebastian Ramacher
wrote:
> On 2022-03-22 20:06:50, Jérémy Lal wrote:
> > On Mon, Mar 21, 2022 at 10:42 PM Sebastian Ramacher <
> sramac...@debian.org>
> > wrote:
> >
> > > Control: tags -1 confirmed
> > >
> > > On 2022-03-21 18:54:38 +0100, Jérémy Lal wrote:
> > >
On 2022-03-22 20:06:50, Jérémy Lal wrote:
> On Mon, Mar 21, 2022 at 10:42 PM Sebastian Ramacher
> wrote:
>
> > Control: tags -1 confirmed
> >
> > On 2022-03-21 18:54:38 +0100, Jérémy Lal wrote:
> > > Package: release.debian.org
> > > Severity: normal
> > > User: release.debian@packages.debian
Processing control commands:
> tags -1 confirmed
Bug #1007906 [release.debian.org] transition: mutter
Added tag(s) confirmed.
--
1007906: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007906
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 confirmed
On Wed, 23 Mar 2022 at 17:21, Simon McVittie wrote:
> The GNOME team is ready for this transition now. As usual, lots of Shell
> extensions are affected by API changes and will need porting or removal,
> but as usual, I think removing the affected Shell extensions from
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
nmu libxxf86vm_1:1.1.4-1+b2 . ANY . unstable . -m "riscv64 arch is at 1:1.1.4-1
while others are at 1:1.1.4-1+b2"
16 matches
Mail list logo
