[arch-dev-public] Disowned python/flask packages

2020-01-01 Thread Antonio Rojas via arch-dev-public
They were dependencies of the obsolete sage-notebook and I no longer need 
them:


python-flask-autoindex
python-flask-silk
python-flask-oldsessions
python-flask-babel
python-speaklater

I will drop the ones that are not needed by anything to AUR if nobody 
adopts them in a week.


Re: [arch-dev-public] soyuz (pkgbuild.com) server move to homedir.archlinux.org

2020-01-01 Thread Sven-Hendrik Haase via arch-dev-public
On Fri, 13 Dec 2019 at 08:00, Sven-Hendrik Haase 
wrote:

> On Mon, 18 Nov 2019 at 07:34, Sven-Hendrik Haase 
> wrote:
>
>> Hi all,
>>
>> I set up a new Hetzner VPS that is going to become our new
>> homedir/public_html server available to all TUs and Devs like soyuz was. We
>> decided to decommission soyuz and put the public_html stuff on its own
>> server for security reasons, to cut costs, and so that we can
>> compartmentalize further.
>>
>> The server uses a Hetzner Cloud Volume which we can scale if we want but
>> for now, it's 100GiB of zstd-compressed btrfs. If possible, we'd like to
>> keep it at this size for the time being. You can host your own repos there
>> if you want and that's fine. Please talk to us beforehand if you see
>> yourself exhausting the volume with what you want to do.
>>
>> If you had stuff hosted in the public_html of soyuz, I'd ask you to
>> transfer stuff over to the new box which is already reachable at the names
>> pkgbuild.com (you'll get an SSH error because of this) and
>> homedir.archlinux.org. Please check if you can throw away some old
>> stuff/junk that you might not necessarily need on the new server.
>>
>> This new box is *not for building*. That's what dragon is for. Please
>> only put documents/files onto the new pkgbuild.com that you actually
>> want people to be able to access publicly. The box has no building
>> facilities and you get no sudo'd commands.
>>
>> soyuz is going to be decommissioned no sooner than 2020-01-01 but do not
>> expect it to hang around for long after that. We will not transfer any
>> files for you from soyuz. In other words: All data not explicitly
>> transferred by you will be destroyed after 2020-01-01.
>>
>> Please bring up any problems you might have with this new server on the
>> arch-devops list or IRC (#archlinux-devops).
>>
>> Enjoy,
>> Sven
>>
>
> This is a short reminder that this is happening. soyuz is going away soon.
> I'll mark it for cancellation one of these days. If you haven't done so
> yet, please migrate your data if it's important.
>

It's 2020 and you know what that means: soyuz has been securely wiped and
canceled. If there is anything you might have forgotten to save, we got
backups to restore it from.


Re: [arch-dev-public] zstd rollout complete

2020-01-01 Thread Jelle van der Waa
On 12/27/19 at 07:10pm, Sven-Hendrik Haase via arch-dev-public wrote:
> On Fri, Dec 27, 2019, 16:31 Robin Broda via arch-dev-public <
> arch-dev-public@archlinux.org> wrote:
> 
> > Hello everyone,
> >
> > We have just tested and released everything necessary for zstd packages in
> > our repos.
> >
> > Right now, the updated devtools is still in [testing],
> > but our preliminary testing shows that nothing immediately combusted on
> > release, so I'm confident.
> >
> > Once it has left testing, packages built with devtools will automatically
> > use zstd with the correct options.
> >
> > There is no intervention necessary, this should be an essentially
> > transparent process.
> >
> >
> > Happy packaging and greetings from 36c3.
> >
> 
> We found out that the historical archive uploader is broken as python
> doesn't have native zstd support in the tarfile package. We're trying to
> fix this currently.

Sadly tarfile does not support .zst so we need to use xtarfile. But
xtarfile does not handle our way of opening package files with
tarfile. [1]

The xtarfile_open method raises a NotImplementedError since it seemingly
does not handle 'r|*' while 'r' works thanks to svenstaro's patch. [2]

Further digging around by removing the '|*' and "encoding='utf-8'" seems
to actually make it workable.. [3]

I'll check if I at least can get it working again...

[1] 
https://github.com/archlinux/arch-historical-archive/blob/master/upload_pkg_internetarchive.py#L42
[2] https://github.com/ascoderu/xtarfile/blob/master/xtarfile/xtarfile.py#L30
[3] https://github.com/ascoderu/xtarfile/issues/3


signature.asc
Description: PGP signature