://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/lyrebird/
--
meskio | https://meskio.net/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
My contact info: https://meskio.net/crypto.txt
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Nos vamos a Croatan.
signature.asc
Description
o debian, it
makes total sense.
I clearly lack the time to work on this package, and I'll be happy to hand it
over if you or someone else wants to maintain it.
Sorry for the long delay to respond.
--
meskio | https://meskio.net/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
My contact
Hello,
I'm one of the maintainers of lyrebird at the Tor Project. I'm happy to help
with the process of getting lyrebird in debian, debian is used by many bridge
operators that will need an easy way to get lyrebird installed.
I'm happy to help with this process.
--
Package: wnpp
Severity: normal
X-Debbugs-Cc: t...@packages.debian.org
Control: affects -1 + src:tudu
I intend to orphan the tudu package.
The package description is:
ToDo list manager in ncurses, with hierarchical representation of the tasks.
Each task has:
* Title
* Long text description
Package: wnpp
Severity: normal
X-Debbugs-Cc: a...@packages.debian.org
Control: affects -1 + src:acr
I intend to orphan the acr package.
The package description is:
ACR is an autoconf like tool that allows you to create configure scripts for
your programs. The main aim of this tool is to teach d
Package: libgl1-mesa-dri
Followup-For: Bug #1025297
Dear Maintainer,
I think I'm seeing the same issue using qubes (xen virtualization), when
I upgraded to 22.3.0-1. Rolling back to 22.2.4-1 solved the problem.
My stacktrace is a bit different:
(==) Log file: "/home/user/.local/share/xorg/Xorg.
Package: obfs4proxy
Version: 0.0.14-1
Severity: important
Dear Maintainer,
obfs4proxy is normally used in comvination with tor either to connect to
a bridge or to provide a bridge. The upgrade will not be taking into
account unless tor is restarted.
Many bridge operators will update automaticall
and if we should upload laminar to experimental or wait for
it to be in sid.
[0] https://packages.debian.org/experimental/capnproto
--
meskio | https://meskio.net/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
My contact info: https://meskio.net/crypto.txt
-=-=-=-=-=-=-=-=-=-=-=-=-=-=
kage
> capnproto quickly with the next release. Right now, Debian's 0.7
> version is quite dated...
--
meskio | https://meskio.net/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
My contact info: https://meskio.net/crypto.txt
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Nos
I'm working on the snowflake package. I have a package that works:
https://gitlab.torproject.org/meskio/snowflake-debian
Looking for a mentor to review it and a place to put it in salsa, I'm asking
the
go-team to see if it will fit under their umbrella.
--
meskio | https://
Package: golang-github-smartystreets-assertions-dev
Version: 1.10.1+ds-1
Severity: normal
Dear Maintainer,
The debian package of github.com/smartystreets/assertions does unvendor
github.com/jacobsa/oglematchers, but the vendored version in the
assertions library did include some improvements. The
in which circumstances this actually happens.
Good luck with it. If you don't find anything we can open an issue upstream,
Oliver is pretty responsive and helpful.
--
meskio | https://meskio.net/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
My contact info: https://meskio.net/crypto.tx
issue: /var/log/laminar.log isn't pre-created and
> daemon drops permissions before creating the file, so it fails
> creating it altogether.)
>From that report I guess you use sysv-init instead of systemd isn't it? Maybe
the SIGPIPE error is also related to that. I have to say I d
ppy to get some help here.
--
meskio | https://meskio.net/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
My contact info: https://meskio.net/crypto.txt
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Nos vamos a Croatan.
signature.asc
Description: signature
-3+
* Vcs : https://salsa.debian.org/meskio-guest/laminar/
Section : devel
It builds those binary packages:
laminard - lightweight and modular continuous integration serviceu (server)
laminarc - lightweight and modular continuous integration service (client)
laminar - light
I'm a happy user of starship and I will love to see it in debian. Is there any
news about this package? Any blockers?
Thanks for working on it.
--
meskio | http://meskio.net/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
My contact info: http://meskio.net/crypt
ymore, but I can't guarantee that the UMD build
> will work in the browser because I have no time to test it (for example in
> laminar UI).
>
> meskio, can you test laminar with the new build ? Thanks
I have tried the new build from the salsa ci[0], but laminar package doesn't
w
Quoting Dmitry Bogatov (2020-03-12 01:26:10)
>
> [2020-02-27 11:40] meskio
> > Dmitry, I see the issue on vue-router.js has being solved since some
> > months. But
> > no movement has being happening in this ITP. Are you still interested on
> > packaging it? Do
s success,
> the laminar service dashboard can be reached from localhost:8080 and causes
> no JavaScript error.
Is there anything still blocking this fix from being uploaded to unstable? Can
I
do something to help here?
Thank you for fixi
://salsa.debian.org/meskio-guest/laminar/
--
meskio | http://meskio.net/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
My contact info: http://meskio.net/crypto.txt
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Nos vamos a Croatan.
signature.asc
Description: signature
n/rules binary subprocess returned exit
status 2
debuild: fatal error at line 1182:
dpkg-buildpackage -us -uc -ui -i -I failed
gbp:error: 'debuild -i -I' failed: it exited with 29
'''
Any idea of what I might be doing wrong? How can I build the package?
Thanks in advance.
--
meskio | http://meskio.net/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
My contact info: http://meskio.net/crypto.txt
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Nos vamos a Croatan.
signature.asc
Description: signature
Quoting Dmitry Bogatov (2019-06-08 12:09:35)
> [2019-06-05 21:26] meskio
> > I see you submitted this ITP for laminar in January. I was wondering
> > what is the status of it and if I can help with it.
>
> Essentially, I stalled on #927254 (in libjs-vue-router dependen
Hello Dimitry,
I see you submitted this ITP for laminar in January. I was wondering what is
the
status of it and if I can help with it.
Thanks for starting the process.
--
meskio | http://meskio.net/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
My contact info: http://meskio.net
Package: infinoted
Version: 0.7.1-1
Followup-For: Bug #810865
Dear Maintainer,
I agree it will be really nice if this patch get merged into infinoted.
I applied the patch to the latest infinoted 0.7.1-1 (beside needing to
update the patch to the new Build-Depends) it works nicely.
Can I do some
ong here.
I submited the bug upstream:
https://github.com/radare/acr/issues/15
I'll try to fix it myself.
--
meskio | http://meskio.net/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
My contact info: http://meskio.net/crypto.txt
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
No
g time for tudu for a long time, not sure if this
will change soon. But I'll wellcome patches ;)
--
meskio | http://meskio.net/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
My contact info: http://meskio.net/crypto.txt
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Nos vamos a Croatan.
signature.asc
Description: signature
Package: yubikey-personalization
Followup-For: Bug #793101
I just found out that my yubikey is a U2F-only key and the
yubikey-personalize tool can't be used with it:
https://www.yubico.com/products/yubikey-hardware/fido-u2f-security-key/#toggle-id-10
I'm not sure if is the same case for the origi
Package: yubikey-personalization
Version: 1.17.2-1
Followup-For: Bug #793101
Dear Maintainer,
I see the same issue in my system. U2F works fine in chromium (I did
modify udev to give me rights no the device, but this is a different
bug). I'm failing on making OTP to work. All the yk* tools tell m
28 matches
Mail list logo
