Hi,
> As an aside, unless something has changed very recently, GH does not
> give you a way to disable PRs (issues yes but not PRs).
>
> If that has suddenly become possible, I have around a thousand
> projects I help maintain upstream on a non-GitHub (open source) code
> forge and would love to
Hi,
> have you considered dgit?
no, as that's something entirely different. dgit does not
manage source packages in Git, it provides a Git frontend
to source packages not managed in Git.
-nik
signature.asc
Description: PGP signature
Hi,
On Mon, Aug 21, 2023 at 09:48:26AM -0700, Russ Allbery wrote:
> Dominik George writes:
>
> > For the GitHub case, the problematic terms would be that in order to
> > register for a GitHub account, users must be at least 13 or 16 years old
> > (depending on the ju
Heisann,
[ for reference, the general discussion was held in 2019 already, in a slightly
]
[ too big context [3].
]
as many of you will know, I am heavily involved in tearing down obstacles
in the way of contributing to free and open sour
Hi Marvin,
>This is simply and blatantly incorrect. Debian is a distribution.
To some, that is the same.
If you think describing Debian as an "operating system", then for a start, you
should go and propoae to update the banner on the front page of
https://debian.org/
-nik
>The mission you have chosen for yourself, then, is to identify all those
>things in the Debian distribution that are not constitutive of an
>operating system.
That is a major part of the work of a Debian Developer, and the ftp-master team.
Packages are evaluated for eligibility to enter the dist
> So, let's at least be consistent.
Totally agree with that.
Debian is not a collection of harmful content, it is an operating system.
But, unfortunately, there are too many people in the project who think, in the
name of "free speech", protecting racists, nazists, and anarchists is more
impor
Package: wnpp
Severity: wishlist
Owner: Dominik George
X-Debbugs-Cc: debian-devel@lists.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
* Package name: rdflib-sqlalchemy
Version : 0.5.4
Upstream Contact: Mark Watts
* URL : https://github.com/RDFLib/rdflib
Package: wnpp
Severity: wishlist
Owner: Dominik George
X-Debbugs-Cc: debian-devel@lists.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
* Package name: netbird
Version : 0.8.5
Upstream Author :
* URL : https://netbird.io/
* License : BSD-3-clause
Hi,
thanks for finally providing this!
> Mails sent via this server will be DKIM-signed if the from is a
> debian.org, debconf.org or ftp-master.debian.org address. If any
> additional domain should be considered, feel free to ask.
I just wanted to make you aware of something interesting I lear
Package: wnpp
Severity: wishlist
Owner: Dominik George
X-Debbugs-Cc: debian-devel@lists.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
* Package name: inkscape-silhouette
Version : 1.25
Upstream Author : Fab Lab Region Nuernberg e. V.
* URL : https
Package: wnpp
Severity: wishlist
Owner: Dominik George
X-Debbugs-Cc: debian-devel@lists.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
* Package name: aleksis-core
Version : 2.0
Upstream Author : The AlekSIS Team
* URL : https://aleksis.org/
* License
Package: wnpp
Severity: wishlist
Owner: Dominik George
* Package name: golang-github-vmware-vmw-ovflib
Version : 0.0~git20200204.53a0e9f-1
Upstream Author : VMware, Inc.
* URL : https://github.com/vmware/vmw-ovflib
* License : Apache-2.0
Programming Lang: Go
Package: wnpp
Severity: wishlist
Owner: Dominik George
* Package name: golang-github-pin-tftp
Version : 2.2.0-1
Upstream Author : Dmitri Popov
* URL : https://github.com/pin/tftp
* License : Expat
Programming Lang: Go
Description : TFTP server and
Package: wnpp
Severity: wishlist
Owner: Dominik George
* Package name: golang-github-vincent-petithory-dataurl
Version : 0.0~git20191104.d1553a7-1
Upstream Author : Vincent Petithory
* URL : https://github.com/vincent-petithory/dataurl
* License : Expat
Package: wnpp
Severity: wishlist
Owner: Dominik George
* Package name: golang-github-coreos-vcontext
Version : 0.0~git20210903.c22998b-1
Upstream Author : CoreOS
* URL : https://github.com/coreos/vcontext
* License : Apache-2.0
Programming Lang: Go
Package: wnpp
Severity: wishlist
Owner: Dominik George
* Package name: ignition
Version : 2.12.0-1
Upstream Author : CoreOS
* URL : https://github.com/coreos/ignition
* License : Apache-2.0
Programming Lang: Go
Description : First boot installer and
Package: wnpp
Severity: wishlist
Owner: Dominik George
* Package name: golang-github-coreos-go-json
Version : 0.0~git20200220.5ae6071-1
Upstream Author : CoreOS
* URL : https://github.com/coreos/go-json
* License : TODO
Programming Lang: Go
Description
Package: wnpp
Severity: wishlist
Owner: Dominik George
* Package name: golang-github-vmware-vmw-guestinfo
Version : 0.0~git20200218.687661b-1
Upstream Author : VMware
* URL : https://github.com/vmware/vmw-guestinfo
* License : Apache-2.0
Programming Lang: Go
Hi,
On Wed, Sep 01, 2021 at 12:04:13AM +, Holger Levsen wrote:
> Moin!
>
> I'm glad to finally be able to send out this invitation for the "Debian
> Reunion
> Hamburg 2021" taking place at the venue of the 2018 & 2019 MiniDebConfs!
>
> The event will run from Monday, Sep 27 2021 until Frida
> > But neither winetricks nor lutris are wrapper packages for
> > non-free programs — while they do allow installing and using non-free
> > software as well, they can be used for any kidn of game or program,
> > including free software. Lutris actually has explicit support for quite a
> > few
> >
Hi,
I have stumbled across this note, in the d/copyright file of the
lutris package:
> Comment: lutris is not part of the Debian distribution, but is in the contrib
> archive area instead, because while lutris itself is free software, its main
> purpose is to download and install mainly non-fre
> In the latter, we should all
>diverge away (more than was already done) from the FSF and lead the Free
>Software movement without the FSF.
I take it that this probably involves Organisations like SPI, who consider it
ok to foster platforms like Zoom, or even worse like LPI, who consider it ok
Hi,
> The problem is that for good reason, we no longer trust the FSF under
> its current governance to do that. What you are affectively asking
> people to do is to pursue justice in regard to things rms did in a forum
> where rms has much more power than they do and where rms (and the voting
>
> 2) It's not something like "this hurts me, please do Debian
>great again - or I'll leave". I'm not in the camp of SJW's and won't
>share their methods.
You're right, it's more something like "mimimi, I will leave now
because I want to make a point, maybe try to come back later, but in
a
Hi,
On Fri, Mar 26, 2021 at 11:50:31AM +0100, Jonas Smedegaard wrote:
> [replying only to -vote - please avoid cross-posting!]
OK, but you actually replied only to -devel instead of -vote.
>
> Quoting Dominik George (2021-03-26 11:05:26)
> > Hi,
> >
> > > A Gener
Hi,
> A General Resolution has been started about Richard Stallman's
> readmission to the FSF board.
>
> It currently has 1 available options, but other proposals have been suggested.
I explicitly do NOT support this GR.
My opinion, as laid out at
https://github.com/rms-open-letter/rms-open-let
Package: wnpp
Severity: wishlist
Owner: Dominik George
X-Debbugs-Cc: debian-devel@lists.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
* Package name: python-telethon
Version : 1.19.0
Upstream Author : Lonami Exo
* URL : https://github.com/LonamiWebs
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-devel@lists.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
* Package name: signald
Version : 0.11.1
Upstream Author : Finn Herzfeld
* URL : https://gitlab.com/signald/signald
* License : GPL
P
Hi,
> in order to allow more people to process the usual routine of
> non-controversial applications, we are now allowing Front Desk members
> to approve applications without the need for a Debian Account Manager.
in case I missed it, what is the background of this decision? Are
there so many NM
Hi,
On Thu, Oct 29, 2020 at 04:59:53PM -0300, Rogério Brito wrote:
> Since the tree was taken down (and, to boot, of the 18 forks listed in the
> takedown request, mine was explicitly listed), I fear that me uploading the
> lastest tree to GitHub is asking for trouble.
>
> Given this situation, c
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
* Package name: gnome-pass-search-provider
Version : 0.0~20191115+da2db41
Upstream Author : Jonathan Lestrelin
* URL : https://github.com/jle64/gnome-pass-search
>PS: I really used real scissors and real glue to cut and paste text, so
>I'm having less problems with metaphors, but I think most metaphors are
>just wrong (I need to learn what they do, and then maybe I learn later
>what it was the origin). We are supposed to make computer easy, but we
>use
>Longer answer: it’s complicated, but I’m sure there’s
>a set of bind and non-bind mounts that will work for
>systemd as well.
>
>Back to topic now. Or I’m going pet the cat.
Well, it *is* on topic. I have been using the same strategy for sysvinit and
systemd systems for many years with great suc
>than you think, either bind-mount tons of filesystem from the host,
>and this is only safe-ish if both run sysvinit
Like most of the time, your allegation is lacking any facts and sources.
Why should that not work on systemd?
-nik
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
> I'm hurt reading your message and Holger's.
> I wrote to the project saying that the current situation sucked for me.
> I got some great offers of help and I think this issue will be easy to
> resolve.
>
> But then I got a message from holger
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
* Package name: upass
Version : 0.3.0
Upstream Author : Chris Warrick
* URL : https://github.com/Kwpolska/upass
* License : BSD-3-clause
Programming Lang
Hi,
> On Sun, Mar 10, 2019 at 03:14:07PM -0400, Reinhard Tartler wrote:
> > I am undecided whether or not this package should be included in Debian
> > 10 (aka buster). It clearly is useful to many people, but its long-term
> > maintenance is unclear.
>
> keepassxc is also going to be in Debian 1
Hi everybody,
here is a short report from the bug squashing party, which took place at
tarent solutions GmbH[1], Bonn, Germany, the last weekend. It was
poartially sponsored by tarent solutions and partially by Teckids[2], with
tarent sponsoring rooms and drinks, and Teckids sponsoring network and
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: python-asttokens
Version : 1.1.13
Upstream Author : Dmitry Sagalovskiy
* URL : https://pypi.org/project/asttokens/
* License : Apache-2.0
> Basically you would like to build an architecture equivalent to Ubuntu's
> PPA
No. Please at least try reading the thread first - it was explicitly
explained several times that this has absolutely nothing to do with the
idea of PPAs.
-nik
signature.asc
Description: PGP signature
Den 27. desember 2018 12:30:33 CET, skrev Holger Levsen :
>On Wed, Dec 26, 2018 at 11:37:21PM +0100, Dominik George wrote:
>> As long as the package is in -volatile
>
>FYI: as long as this proposal is been presented with the name -volatile
>it's dead to me and saves me fro
Hi,
> How to handle upgrades from stable to stable+1. Packages from backports
> upgrade with no issues as stable+1 contains the same packages already
> compiled for the stable+1.
As long as the package is in -volatile, it is not in stable+1, and
upgrades are ensured by the volatile maintainer. If
> For backports the general supportability assumption is that you provide a
> sane upgrade path from stable to the backports and from the backport to the
> next stable (optimally the same package). Once you take the presence of the
> stable package out of the mix, it becomes weird. How long do you
> - Should the package begin to migrate to testing again, it must
>be moved to stable-backports.
>
> - Using the same ~bpo version namespace
Both of these poitns are there to *not* change anything about backports.
If a package stops qualifying for -volatile, and starts qualifying for
-backp
> > - The package must not be in testing, and care must be taken for the
> > package not to migrate to testing.
> So what would a user of testing do? Will there be a $codename-volatile[1]
> suite for testing users? Or would they directly install unstable with no
> other pre-release staging gr
Hi,
> 2. I am happy with the current charter of backports and I think it's
> possible to move forward with fastpaced without having to change
> that charter.
Yep. That's exactly why the proposal changes nothing about -backports. I
am still confused why Alex and you keep insisting that an
> >If there are other issues to solve than the lifespan of the package
> >version, they must be solved in another way.
>
> I agree with you, it is the best outcome. But when people with power
> (-backports ftp masters) are not willing to consider it, we have to go
> with plan B, which is less than
> I don't want backports to contain things are are not suited for a
> release.
That's why we are doing all this. It is NOT about anything to backports.
It is about adding something new that uses the same RULES as backports,
with a slight diversion, and thus can also make use of infrastructure
alre
Hi,
On Wed, Dec 26, 2018 at 03:05:55PM +0100, gregor herrmann wrote:
> (Can we keep this on one mailing list, please? /me restricts this to
> -devel)
No. This has the potential of keeping people who are directly impacted
by this proposal out of the loop.
> And besides that, I think the more univ
>> I actually think volatile is a good name. After all, it's not so far
>from the previous volatile.
>
>volatile is a very bad name for this because we've used it already for
>something else.
Well, I consider it more or less the same basic idea. The old and new ideas
have more in common than not,
> - no need to keep a volatile package out of testing
Oh, and yes. Having a package in testing means it will be supported for a
stable lifecycle - a full contradiction to volatile!
-nik
Hi,
>I would, however, completely separate it from backports. I.e.
>
> - separate NEW queue
> - different suffix
> - no need to keep a volatile package out of testing
>
>Why?
>
> - volatile is a different beast from backports, this should be
> very clear to both package maintainers and our users
>Just to make things a bit clearer for people who may not have followed
>some of the discussions on d-bp-users lately: the point is to be able
>to
>support fast-moving software with not-so-fast moving dependencies;
>the dependencies may easily be backported without too large a burden
>(their versio
Hi,
I like the general direction, but there are some aspects of your
>proposal
>which should be improved.
Thanks!
>> Other ideas: fastlane, unsupported
>
>Or maybe something like "fastpaced", after all this repo would not be
>unsupported at all, the very point is to provide actual support after
Hi,
>having read the whole Gitlab discussion, I still don't get how/why the
>new repository depends or relates to backports. Instead it could be
>self-contained, except for stuff already available in stable. Couldn't
>you roll the new repository entirely independent of any backports? Even
>if you
> In short: This proposal addresses the exact concerns you raised before
> )although I am not the person you expressed them towards).
Well, sure, I was involved in that thread, but only in the way that I
announced a proposal (this one). Not in any of the stuff concerning
adding something to -backp
On Tue, Dec 25, 2018 at 10:11:43PM +0100, Alexander Wirt wrote:
> https://lists.debian.org/debian-backports/2018/12/msg00028.html
>
> This wasn't about gitlab.
Oh. I must have misread the "gitlab" in the subject, along withthe mail
being sent to the gitlab maintainer, a gitlab bugreport in the B
> We already told you to build your own repo.
You should probably start with identifying the senders of mail
correctly ☺. I am not the gitlab maintainer (and will never be).
> Imho you should start the same way backports started - outside of
> debian.
> Prove that it works and integrate into Debi
Heisann, alle sammen,
as announced in the recent thread about maintaining, I hereby propose a
repository that allows making “backports” of packages available to users
of the stable distribution, if those packages cannot be maintained in
testing and backported in the usual way. If you are intereste
>> We had volatile, which, redefined properly, could help. I am trying
>to draft such a definition.
>
>Did you get a chance to work on it?
I do have this on my todo list for around Christmas.
People who know me that I deliberately leave out the year, but my intentions
are 2018 ;).
-nik
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: ratchet-pawl
Version : 0.3.2
Upstream Author : Chris Boden
* URL : https://github.com/ratchetphp/Pawl
* License : MIT
Programming Lang
Hi everybody,
situation is as follows:
I have a package (movim) which just got accepted into sid, and used to
work properly. It now turns out that it is broken with PHP 7.3 - or
rather, php-zmq has issues with PHP 7.3 [1].
Now the situation is as follows:
* The bug is in php-zmq, but only with
> Your thoughts?
sid is not a rolling release for the public, it is a development area.
Some users use it as a rolling release to get bleeding edge software,
but in fact they become a developer that way (not meaning DD).
If you think regular development prevents you from staying up to date
durin
> I don't think that you can claim that the act of sending a mail to a
> list @lists.debian.org can constitute an implied agreement to accept and
> abide by the code of conduct. That is no different than "by reading
> this, you are bound by these terms." No reasonable person would
> consider eith
> > he agreed with the CoC,
>
> He did not, the CoC didn't exist yet 14 years ago.
He did, if not before, when he sent his mail to a mailing list
@lists.debian.org.
He might not have realised that, of course.
-nik
signature.asc
Description: PGP signature
>But at the same time, I consider mine a very polite answer, without any
>particularly accusatory wording or anything like that, nor I consider
>any of what I wrote worthy of being replied with:
>Fuck you. Do not contact me again. I shall consider
>any further contact (from you or anyone else
Hi,
>that is fine in general. Since Python 2 is supported in Buster, please
>use severity: normal for now. Most of these games are considered to be
>complete and/or no longer supported upstream. If we want to preserve as
>many of those games as possible, we should come up with a plan how we
>can p
Hi,
as the maintainer of pygame, I'd like to bring the move to Python 3 forward,
and thus intend to ask all rdepends that are applications to try and move to
python3-pygame.
The packages are:
angrydd
ardentryst
bambam
bouncy
bubbros
childsplay
deluge-gtk
ffrenzy
fofix
freealchemist
fr
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: shelltux
Version : not yet a versioned release
Upstream Author : Gregor Mitsch
* URL : https://framagit.org/feinstaub/shelltux
* License
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: tic80
Version : 0.70.6
Upstream Author : Vadim Grigoruk
* URL : https://tic.computer
* License : Expat
Programming Lang: C
Description
Hi,
> I don't think categorizing these things as spam is the right thing to do
> -- although ignoring them most of the time is.
If they don't care enough about privacy and free software before doing a
survey in a privacy and free software community using privacy and free
software ignorant tools,
Hi,
>However, your choice of involving Google in this "anonymized" survey
>strongly discourages me personally from participating.
Me too.
I will not take part in a survey needlessly using non-free spyware.
-nik
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: reactphp-socket
Version : 0.8.11
Upstream Author : Igor Wiedler, Chris Boden
* URL : https://github.com/reactphp/socket
* License : MIT
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: reactphp-promise-stream
Version : 1.1.1
Upstream Author : Christian Lück
* URL : https://github.com/reactphp/promise-stream
* License : MIT
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: reactphp-dns
Version : 0.4.13
Upstream Author : Igor Wiedler, Chris Boden
* URL : https://github.com/reactphp/dns
* License : MIT
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: reactphp-stream
Version : 0.7.7
Upstream Author : Igor Wiedler, Chris Boden
* URL : https://github.com/reactphp/stream
* License : MIT
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: reactphp-cache
Version : 0.4.2
Upstream Author : Igor Wiedler, Chris Boden
* URL : https://github.com/reactphp/cache
* License : MIT
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: evenement
Version : 3.0.1
Upstream Author : Igor Wiedler
* URL : https://github.com/igorw/evenement
* License : MIT
Programming Lang: PHP
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: reactphp-promise-timer
Version : 1.3.0
Upstream Author : Christian Lück
* URL : https:/github.com/reactphp/promise-timer
* License : MIT
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: reactphp-event-loop
Version : 0.5.2
Upstream Author : Igor Wiedler, Chris Boden
* URL : https://github.com/reactphp/event-loop
* License
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: ratchet-rfc6455
Version : 0.2.4
Upstream Author : Chris Boden
* URL : https://github.com/ratchetphp/RFC6455
* License : MIT
Programming
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: sdaps
Version : 1.2.1
Upstream Author : Benjamin Berg
* URL : https://sdaps.org
* License : GPL-3+ / LPPL
Programming Lang: Python
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: php-react-child-process
Version : 0.5.0
Upstream Author : Cees-Jan Kiewiet
* URL : https://github.com/reactphp/child-process
* License
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: php-encryption
Version : 2.1.0
Upstream Author : Taylor Hornby
* URL : https://github.com/defuse/php-encryption
* License : Expat
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: php-fig-cookies
Version : 1.0.2
Upstream Author : Beau Siemensen
* URL : https://github.com/dflydev/dflydev-fig-cookies
* License : Expat
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: php-buzz-react
Version : 2.1.0
Upstream Author : Christian Lück
* URL : https://github.com/clue/php-buzz-react
* License : Expat
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: php-cocur-slugify
Version : 3.0.1
Upstream Author : Florian Eckerstorfer
* URL : https://github.com/cocur/slugify
* License : Expat
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: php-ramsey-uuid
Version : 3.7.1
Upstream Author : Ben Ramsey
* URL : https://benramsey.com/projects/ramsey-uuid/
* License : Expat
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: php-respect-validation
Version : 1.1.14
Upstream Author : Henrique Moody
* URL : http://respect.github.io/Validation/
* License : BSD
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: php-react-http
Version : 0.7.4
Upstream Author : Chris Boden
* URL : https://github.com/reactphp/http
* License : Expat
Programming Lang
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: php-ratchet
Version : 0.4
Upstream Author : Chris Boden
* URL : http://socketo.me/
* License : Expat
Programming Lang: PHP
Description
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: twemoji
Version : 2.3
Upstream Author : Twitter Inc.
* URL : http://twitter.github.io/twemoji/
* License : Expat, CC-BY
Programming Lang
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: php-emoji
Version : 1.0.0
Upstream Author : Tom Graham
* URL : https://github.com/heyupdate/emoji
* License : Expat
Programming Lang: PHP
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: nano-assault
Version : 1.0
Upstream Author : Eike Jesinghaus
* URL : https://edugit.org/eike/nanoassault
* License : GPL
Programming Lang
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: bdist-nsi
Version : 0.1.5
Upstream Author : Amorilia
* URL : https://pypi.python.org/pypi/bdist_nsi
* License : BSD
Programming Lang
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: leaflet-contextmenu
Version : 1.4.0
Upstream Author : Adam Ratcliffe
* URL : https://github.com/aratcliffe/Leaflet.contextmenu
* License
u haven't seen a fast VNC session at full HD
either ;).
0.9.1-7 will be in jessie-backports, though.
-nik
--
PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296
Dominik George · Hundeshagenstr. 26 · 53225 Bonn
Mobile: +49-1520-1981389 · https://www.dominik-george.de/
Tecki
ask for an unblock,
which seems to be also possible for bugs with important severity.
-nik
--
PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296
Dominik George · Hundeshagenstr. 26 · 53225 Bonn
Mobile: +49-1520-1981389 · https://www.dominik-george.de/
Teckids e.V. · FrOSCon e.V
never know what clients will use it.
The patch that upstream has is less than 5 lines.
Should I report and handle this as an RC bug and request unblock in
Debian?
-nik
--
PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296
Dominik George · Hundeshagenstr. 26 · 53225 Bonn
Mobile
1 - 100 of 174 matches
Mail list logo
