Package: wnpp
Severity: wishlist
Owner: Agathe Porte
X-Debbugs-Cc: debian-devel@lists.debian.org, deb...@microjoe.org
* Package name: python-pyrcb2
Version : 0.6.2
Upstream Author : taylor.fish
* URL : https://github.com/taylordotfish/pyrcb2
* License : LGPLv3
On Tue, 2022-03-01 at 15:24 +0200, Jonathan Carter wrote:
> Hi Phil (and everyone)
>
> On 2022/03/01 15:10, Philip Wyett wrote:
> > Thank you for the terse response. The two examples i.e. micronews and the
> > infra list do not
> > sound
> > that this is scheduled work at all. Better communicatio
Package: wnpp
Owner: Dirk Eddelbuettel
Severity: wishlist
* Package name: r-cran-tiledb
Version : 0.11.0
Upstream Author : TileDB Inc
* URL or Web page : https://github.com/TileDB-Inc/TileDB-R
* License : MIT
Description : R Interface to the TileDB Storage Engine
Hi Phil (and everyone)
On 2022/03/01 15:10, Philip Wyett wrote:
Thank you for the terse response. The two examples i.e. micronews and the infra
list do not sound
that this is scheduled work at all. Better communication from teams would
possibly give better
understanding and the patience of use
On Tue, 2022-03-01 at 12:56 +, Andrew M.A. Cater wrote:
> On Tue, Mar 01, 2022 at 12:09:17PM +, Philip Wyett wrote:
> > On Tue, 2022-03-01 at 12:48 +0100, a a wrote:
> > > Hi.
> > >
> > > Today a tried to access contents of debian instaler git repository on
> > > salsa.debian.org and
> >
On Tue, Mar 01, 2022 at 12:09:17PM +, Philip Wyett wrote:
> On Tue, 2022-03-01 at 12:48 +0100, a a wrote:
> > Hi.
> >
> > Today a tried to access contents of debian instaler git repository on
> > salsa.debian.org and the
> > server responded with 403 error. Next i tried other content located
On Tue, 2022-03-01 at 12:48 +0100, a a wrote:
> Hi.
>
> Today a tried to access contents of debian instaler git repository on
> salsa.debian.org and the
> server responded with 403 error. Next i tried other content located on said
> server with the same
> resposne. Was there a change in access p
On 3/1/22 12:48, a a wrote:
Today a tried to access contents of debian instaler git repository on
salsa.debian.org and the server responded with 403 error. Next i tried
other content located on said server with the same resposne. Was there a
change in access policy or something is wrong with the
Hi.
Today a tried to access contents of debian instaler git repository on
salsa.debian.org and the server responded with 403 error. Next i tried
other content located on said server with the same resposne. Was there a
change in access policy or something is wrong with the server itself.
Thank You
Hi!
On Tue, 2022-03-01 at 10:28:28 +0100, Julien Puydt wrote:
> one of my package has a failure on mips64el and upstream is ready to
> help me find the cause and debug the issue.
>
> Unfortunately, on https://db.debian.org/machines.cgi I only see five
> developer machines on this architecture --
On 3/1/22 10:54, Julien Puydt wrote:
Le mardi 01 mars 2022 à 10:34 +0100, Sebastiaan Couwenberg a écrit :
On 3/1/22 10:28, Julien Puydt wrote:
Is there really no mips64el porterbox, or is it only a transitory
situation?
eller.debian.org has mips64el chroots.
How do I use one of those and n
On Tue, Mar 1, 2022 at 10:28 AM Julien Puydt wrote:
> Hi,
>
> one of my package has a failure on mips64el and upstream is ready to
> help me find the cause and debug the issue.
>
> Unfortunately, on https://db.debian.org/machines.cgi I only see five
> developer machines on this architecture -- al
Le mardi 01 mars 2022 à 10:34 +0100, Sebastiaan Couwenberg a écrit :
> On 3/1/22 10:28, Julien Puydt wrote:
> > Is there really no mips64el porterbox, or is it only a transitory
> > situation?
>
> eller.debian.org has mips64el chroots.
>
How do I use one of those and not a mipsel one? I'm using
Julien Puydt writes:
> Hi,
>
> one of my package has a failure on mips64el and upstream is ready to
> help me find the cause and debug the issue.
>
> Unfortunately, on https://db.debian.org/machines.cgi I only see five
> developer machines on this architecture -- all buildd!
>
> Is there really
mips64el uses the same porterbox with mipsel, since mips32 and mips64 are
compatiable; and all of our machines are in fact 64bit.
Julien Puydt 于 2022年3月1日周二 下午5:28写道：
> Hi,
>
> one of my package has a failure on mips64el and upstream is ready to
> help me find the cause and debug the issue.
>
>
On 3/1/22 10:28, Julien Puydt wrote:
Is there really no mips64el porterbox, or is it only a transitory
situation?
eller.debian.org has mips64el chroots.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Hi,
one of my package has a failure on mips64el and upstream is ready to
help me find the cause and debug the issue.
Unfortunately, on https://db.debian.org/machines.cgi I only see five
developer machines on this architecture -- all buildd!
Is there really no mips64el porterbox, or is it only a
17 matches
Mail list logo
