No mips64el porterbox?

2022-03-01 Thread Julien Puydt
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 transitory
situation?

Cheers,

J.Puydt



Re: No mips64el porterbox?

2022-03-01 Thread Sebastiaan Couwenberg

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



Re: No mips64el porterbox?

2022-03-01 Thread YunQiang Su
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.
>
> 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 transitory
> situation?
>
> Cheers,
>
> J.Puydt
>
>


Re: No mips64el porterbox?

2022-03-01 Thread Gard Spreemann

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 no mips64el porterbox, or is it only a transitory
> situation?

Hi,

How about eller.debian.org?

 $ uname -a
 Linux eller 4.19.0-18-octeon #1 SMP Debian 4.19.208-1 (2021-09-29) mips64 
GNU/Linux
 $ lscpu
 Architecture:mips64
 Byte Order:  Little Endian


-- Gard


signature.asc
Description: PGP signature


Re: No mips64el porterbox?

2022-03-01 Thread Julien Puydt
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
https://dsa.debian.org/doc/schroot/ as usual, and it looks like I'm
getting a mipsel and not mips64el...

Thanks,

J.Puydt



Re: No mips64el porterbox?

2022-03-01 Thread Jérémy Lal
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 -- all buildd!
>

The "architecture" column filter is not the one to use to find a porter box
for a given architecture,
that's why you did not find it.

Jérémy


Re: No mips64el porterbox?

2022-03-01 Thread Sebastiaan Couwenberg

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 not a mipsel one? I'm using
https://dsa.debian.org/doc/schroot/ as usual, and it looks like I'm
getting a mipsel and not mips64el...


Specify the mips64el chroot when creating it:

 schroot -b -c sid_mips64el-dchroot -n $sessionid

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1



deb-porterbox (was: Re: No mips64el porterbox?)

2022-03-01 Thread Guillem Jover
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 -- all buildd!
> 
> Is there really no mips64el porterbox, or is it only a transitory
> situation?

As others have mentioned there's one such box. You can use the
following script to get the available porterbox for any arch:

  

I'll check whether I did submit that to something like devscripts,
which I cannot recall.

Thanks,
Guillem



access forbiden salsa.debian.org

2022-03-01 Thread a a
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

Have A nice Day


Re: access forbiden salsa.debian.org

2022-03-01 Thread Sebastiaan Couwenberg

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 server itself.


See: 
https://lists.debian.org/debian-infrastructure-announce/2022/02/msg0.html


Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1



Re: access forbiden salsa.debian.org

2022-03-01 Thread Philip Wyett
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 policy or something is wrong with the 
> server itself.
> 
> Thank You
> 
> Have A nice Day

See: https://micronews.debian.org/

Small headline and other than that we are being told nothing.

Regards

Phil

-- 
*** Playing the game for the games own sake. ***

WWW: https://kathenas.org

Twitter: @kathenasorg

IRC: kathenas

GPG: 724AA9B52F024C8B


signature.asc
Description: This is a digitally signed message part


Re: access forbiden salsa.debian.org

2022-03-01 Thread Andrew M.A. Cater
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 said 
> > server with the same
> > resposne. Was there a change in access policy or something is wrong with 
> > the server itself.
> > 
> > Thank You
> > 
> > Have A nice Day
> 
> See: https://micronews.debian.org/
> 
> Small headline and other than that we are being told nothing.
> 
> Regards
> 
> Phil
> 
> -- 
> *** Playing the game for the games own sake. ***
> 
> WWW: https://kathenas.org
> 
> Twitter: @kathenasorg
> 
> IRC: kathenas
> 
> GPG: 724AA9B52F024C8B

t's scheduled work: that is still ongoing - is that good enough?

All the very best, as ever,

Andy Cater



Re: access forbiden salsa.debian.org

2022-03-01 Thread Philip Wyett
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
> > > 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
> > > 
> > > Have A nice Day
> > 
> > See: https://micronews.debian.org/
> > 
> > Small headline and other than that we are being told nothing.
> > 
> > Regards
> > 
> > Phil
> > 
> > -- 
> > *** Playing the game for the games own sake. ***
> > 
> > WWW: https://kathenas.org
> > 
> > Twitter: @kathenasorg
> > 
> > IRC: kathenas
> > 
> > GPG: 724AA9B52F024C8B
> 
> t's scheduled work: that is still ongoing - is that good enough?
> 
> All the very best, as ever,
> 
> Andy Cater
> 

Hi,

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 users/developers that is being asked for.

Regards

Phil

-- 
*** Playing the game for the games own sake. ***

WWW: https://kathenas.org

Twitter: @kathenasorg

IRC: kathenas

GPG: 724AA9B52F024C8B


signature.asc
Description: This is a digitally signed message part


Re: access forbiden salsa.debian.org

2022-03-01 Thread Jonathan Carter

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 users/developers that is being asked for.


Our GitLab instance (Salsa), have fallen behind multiple versions. This 
is due to a bunch of different hurdles that all came with their own 
decisions (I'm going to urge the Salsa admins again to do a write-up 
about it).


So what's happening now is point-to-point upgrades between all the 
GitLab versions needed on this upgrade path, along with the migrations 
between them (which are quite large, Salsa is one of the biggest GitLab 
instances out there).


So while a huge amount of pent up maintenance is all happening at once 
now, at least regular updates (and security updates) will be able to run 
again on short cycles.


(I hope salsa admins don't mind me posting this, but I hope it helps all 
our contributors better understand what's going on).


On a practical note, please take note of any uploads you do during this 
downtime, and be sure to do a git push along with the tags when Salsa is 
back up again.


-Jonathan



Bug#1006652: ITP: r-cran-tiledb -- R Interface to the TileDB Storage Engine

2022-03-01 Thread Dirk Eddelbuettel


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

This also complements the TileDB Python package.

Dirk

-- 
https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org



Re: access forbiden salsa.debian.org

2022-03-01 Thread Philip Wyett
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 communication from teams would 
> > possibly give better
> > understanding and the patience of users/developers that is being asked for.
> 
> Our GitLab instance (Salsa), have fallen behind multiple versions. This 
> is due to a bunch of different hurdles that all came with their own 
> decisions (I'm going to urge the Salsa admins again to do a write-up 
> about it).
> 
> So what's happening now is point-to-point upgrades between all the 
> GitLab versions needed on this upgrade path, along with the migrations 
> between them (which are quite large, Salsa is one of the biggest GitLab 
> instances out there).
> 
> So while a huge amount of pent up maintenance is all happening at once 
> now, at least regular updates (and security updates) will be able to run 
> again on short cycles.
> 
> (I hope salsa admins don't mind me posting this, but I hope it helps all 
> our contributors better understand what's going on).
> 
> On a practical note, please take note of any uploads you do during this 
> downtime, and be sure to do a git push along with the tags when Salsa is 
> back up again.
> 
> -Jonathan
> 

Hi Jonathan,

Many thanks for the update. I hope work progresses well and salsa is available 
again soon post the
work that needs to be performed.

Regards

Phil

-- 
*** Playing the game for the games own sake. ***

WWW: https://kathenas.org

Twitter: @kathenasorg

IRC: kathenas

GPG: 724AA9B52F024C8B


signature.asc
Description: This is a digitally signed message part


Bug#1006663: ITP: python-pyrcb2 -- A powerful asynchronous IRC bot library

2022-03-01 Thread Agathe Porte
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+
  Programming Lang: Python
  Description : A powerful asynchronous IRC bot library

pyrcb2 is an asyncio-based library for writing IRC bots. It is designed
to be easy to use, customizable, and high-level.

pyrcb2 includes features such as account tracking, user prefix tracking
(voice, op, etc.), messaging delaying to prevent throttling, and long
message splitting.

pyrcb2 also makes use of asyncio and coroutines in Python. This allows
you to write asynchronous code in a linear fashion—you can handle
responses to commands right after you send them.

===

I intent to maintain this package under the umbrella of the Debian
Python Team. I need it to properly package an IRC bot designed for the
DPT itself.