Package: wnpp
Severity: wishlist
Owner: Dominik George
* Package name: twittare
Version : 0.7.42
Upstream Author : TabaréCaorsi
* URL : http://www.twittare.com/
* License : GPL-3+
Programming Lang: C++
Description : A Twitter client for Linux written
Hi Thorsten,
while I tend to basically acknowledge your points here, there is still one
thing you obviously did not get until now, if I followed along correctly.
>For example, systemd has support for its own (S)NTP client, but also
>supports xntpd (rudely leaving OpenNTPD out already). The commi
Hi,
I have sent a reply off-list because I do not think the question is really
related to Debian development by itself.
As Teckids is dedicated to teaching Free Software (development) to children
and adolescents, I saw fit here.
Just for your information that someone has taken care of the inqu
>To make it short: I suggest that systemd should only migrate together
>with systemd-shim.
ACK!
-nik
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/8667e39c-b7ef-
Hi,
the libfreerdp1 package changed its soname without a transition and
without introducing a new package.
That broke binary compatibility of at least remmina and
libguac-client-rdp0 [0].
I expect more rebuilds / binNMUs to be necessary. As I do not find
anything about that triggered by the main
>> Array variables practically imply arithmetic evaluation, amd this is
>a
>> shell feature which is rather difficult to use correctly because
>> compatibility with other shell encourages both recursive evaluation
>> and access to the full shell language in a few corners.
I think the idea here was
Hi,
>but it seems there is some dependency in jessie which makes gnome
>unavailable
>without systemd.
It is there because upstream requires it. There is no GNOME without systemd.
This is not specific to Debian.
-nik
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a sub
Hi,
> Le lundi 17 novembre 2014 à 11:15 -0800, Don Armstrong a écrit :
>> §6.3.6 does not prevent the CTTE from being presented an issue early. It
>> stops the CTTE from deciding an issue before a consensus approach has
>> been attempted. In this particular case, I felt that a consensus
>> approac
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
** Prerequisite for geierlein, ITP #695204 **
* Package name: libjs-forge
Version :
Upstream Author : Digital Bazaar, Inc.
* URL : https://github.com
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
** Prerequisite for geierlein, ITP #695204 **
* Package name: libjs-gzip
Version : 0.3.1
Upstream Author : T. Jameson Little
* URL : htts://github.com/beatgammit
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
** Prerequisite for geierlein, ITP #695204 **
* Package name: libjs-jsxml
Version :
Upstream Author : Anton Zorko
* URL : http://jsxml.net
* License : BSD
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: minetest-mod-mesecons
Version : 0~20130821+git96011bc
Upstream Author : Jeija
* URL : http://www.mesecons.net
* License : LGPL-3, CC-BY-SA
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: minetest-mod-worldedit
Version : 1.0
Upstream Author : Dominik George
* License : AGPL-3
Programming Lang: Lua
Description : Minetest mod
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: minetest-mod-pipeworks
Version : 0~20130827+git59362e3d20
Upstream Author : Vanessa Ezekowitz
* License : WTFPL
Programming Lang: Lua
Description
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: minetest-mod-plantlife
Upstream Author : Vanessa Ezetowski
* License : WTFPL, CC-BY-SA-2.0+
Programming Lang: Lua
Description : Minetest mod - Plantlife
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: minetest-mod-moreores
Upstream Author : Calinou
* License : GPL-3+, CC-BY-SA-3.0
Programming Lang: Lua
Description : Minetest mod - More Ores
This mod
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: minetest-mod-moreblocks
Upstream Author : Calinou
* License : zlib/libpng
Programming Lang: Lua
Description : Minetest mod - More Blocks
This mod adds
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: minetest-mod-technic
Upstream Author : RealBadAngel
* License : GPL-2
Programming Lang: Lua
Description : Minetest mod - Technic
All technic stuff for
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: minetest-mod-moretrees
Upstream Author : Vanessa Ezekowitz
* License : WTFPL
Programming Lang: Lua
Description : Minetest mod - more trees
This mod adds
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: minetest-mod-itemdrop
Upstream Author : PilzAdam
* License : WTFPL
Programming Lang: Lua
Description : Minetest mod - Item Drop
This mod adds Minecraft
Hi, maintainers of unar and unrar-free,
as you might have seen on the BTS, I have today filed a bug report on
unrar-free and revisited an old bug, both of which make unrar-free
largely unusable [1][2]. I found that unrar-free seems to be umaintained
and has not had any commits by upstream for the
Howdy,
here is a short update on the progress of the compatibility script.
I have put together a shell script that accepts all command-lines that
unrar-free or unrar-nonfree would accept and correctly parses them into
internal variables. Doing so, I found that:
- Both unrar-free and unrar-nonfr
Hi,
> Not directly related to this, I noticed that unar depends on
> gnustep-base-runtime, which in turn spawns the gdomap daemon. Is this
> thing needed at all?
I also noticed that. It comes from ${shlibs:Depends} in the package, so
I figure it is indeed needed (the runtime, not the gdomap daemo
Hi,
> This all sounds like a great idea, but I would suggest that rather than
> attempt to be command-line compatible with the existing tool, you
> clearly define a set of command line arguments and their corresponding
> semantics that you *do* support, ensuring that it is an accurate and
> correc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Norbert Preining schrieb:
>On So, 29 Sep 2013, Stephen Kitt wrote:
>> > Uninstall the libc6-amd64:i386 package.
>> > See http://lists.debian.org/debian-mentors/2013/03/msg00139.html.
>>
>> But watch out for http://bugs.debian.org/699206 - make sur
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Norbert Preining schrieb:
>Hi Dominik,
>
>> Simply put: Because you made no effort to fix it :).
>
>Thanks for the very useful comment.
>
>Yes, I care for RC bugs in my own packages ... and that are quite
>a lot. So no time to fix RC bugs of other
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Jerome BENOIT schrieb:
>Hello,
>
>I am packaging a versionless library software maintained via a
>mercurial repository.
>Is there any custom for this case ?
>If not, can we use the version format 'hgMMDD' ?
>
>
>Best regards,
>Jerome
I tend t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
>What does 'XX' stand for ?
The short commit hash, as proposed in your initial mail.
>You should use a version derived from the date only. This way, you
>won't be in
>trouble if upstream switches to git.
I absolutely do not see why this s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
>0~MMDD
>
>should be fine.
It isn't, it is not a unique identifier for the one "release" you are packaging.
- -nik
-BEGIN PGP SIGNATURE-
Version: APG v1.0.8-fdroid
iQFNBAEBCgA3BQJSTCxtMBxEb21pbmlrIEdlb3JnZSAobW9iaWxlIGtleSkgPG5p
a0BuYX
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Wookey schrieb:
>+++ Dominik George [2013-10-02 16:23 +0200]:
>>
>> >0~MMDD
>> >
>> >should be fine.
>>
>> It isn't, it is not a unique identifier for the one "release" you are
&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dominique Dumont schrieb:
>On Wednesday 02 October 2013 16:05:18 Dominik George wrote:
>> >You should use a version derived from the date only. This way, you
>> >won't be in
>> >trouble if upstream switches to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
>A packager is not required to serve users with such specific needs.
Hmm, I last saw that attitude when being explained "the Arch way".
I established an advantage for the user using my proposal - go get me a
disadvantage for the packager.
That sa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Vincent Lefevre schrieb:
>Then, do you mean that VCS hashes are sortable?
Of course not. One would have to do something like 0~MMDDnn+git in that
rare case.
My argument for keeping the VCS hash is to ease identifying the code in the
pac
Hi,
I have looked into this a bit.
> Some of the source packages were caught on a gateway anti-virus scanner while
> downloading.
Using a gateway anti-virus scanner for downloads from the Debian archive
seems a bit inappropriate, well, paranoid. Checking the signed hashsums
would seem a lot bett
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Marc Haber schrieb:
>On Tue, 15 Oct 2013 13:19:38 +0200, "Thijs Kinkhorst"
> wrote:
>>I'm missing why the package cannot use the EICAR test virus signature
>for
>>its purposes.
>
>eicar.com does not have a distributable license.
I do not think it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dominik George schrieb:
>I do not think it is actually copyrightable software. It is a string
>that was agreed in to trigger antivirus scanners, so it is more or less
>a protocol. Consider the downloads at eicar.com reference
>imp
Hi,
> The only problem is that on small machines (things like the BeagleBone)
> xz compression requires enough memory that you have to enable swap to
> use dpkg. Now on a machine with a sensible disk this is not a problem,
> but on a machine where the "disk" is an SD-card it is a disaster.
corre
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: morse2ascii
Version : 0.2
Upstream Author : Luigi Auriemma
* URL : http://aluigi.altervista.org/mytoolz.htm
* License : GPL-2
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: dtmf2num
Version : 0.1e
Upstream Author : Luigi Auriemma
* URL : http://aluigi.altervista.org/mytoolz.htm
* License : GPL-2+
Programming
Hi,
> > * Does not depend on replacing init
>
> Wasn’t there some mention of xfce needing gnome-settings-daemon as well,
> which would kinda defeat the point?
Not as far as I can tell:
nik@keks:~ $ apt-rdepends xfce4 | grep gnome
> > xfswitch-plugin -> gdm3 -> gnome-settings-daemon
>
> xfswitch-plugin is suggested by xfce4-goodies, so irrelevant for this
> discussion.
However, I must admit that even if the standard XFCE installation does
not depend on systemd, it would be even worse if a user came along and
wanted to ext
On Fri, Oct 25, 2013 at 01:06:02PM +0100, Jonathan Dowland wrote:
> On Fri, Oct 25, 2013 at 02:02:48PM +0200, Dominik George wrote:
> > However, I must admit that even if the standard XFCE installation does
> > not depend on systemd, it would be even worse if a user came along an
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
* Package name: ssb-sprom
Version : 20120331
Upstream Author : Michael Buesch
* URL : http://linuxwireless.org/en/users/Drivers/b43
* License : GPL-2
Hi,
> is there a proper way to get rid of the recent
> privacy-breach-google-adsense Lintian violation/error report [1] ?
obviously, remove all Adsense and related spyware fetching code from
your package.
Cheers,
Nik
--
* concerning Mozilla code leaking assertion failures to tty without D-BUS
Hi,
> Obviously, but the problem is that the involved html pages correspond to
> the manual of my package so it sounds not reasonable to wipe them out:
> is there any tools that may help to clean up the corrupted html pages ?
I assume there are Adsense images included from the HTML docs in your
p
> I would love to have it *real* fullscreen
>since
>
> f Toggles fullscreen mode.
>
>... but the rendered PDF remains in a small section in the middle of
>the
>window. Not sure whether this is a bug or a feature - but for
>presentations ist seems I need to stick to evince.
Or you cont
>I also read this (I love that short docs) but there is a very thick
>remaining gray frame - it seems the scaling is done only by integer
>numbers which is for sure quick but the result is not what I want.
Hmm. I cannot reproduce that, sorry!
-nik
--
To UNSUBSCRIBE, email to debian-devel-requ
Package: wnpp
Severity: wishlist
Owner: Dominik George
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: nxt-firmware
Version : 1.29-20120908
Upstream Author : Nicolas Schodet
* URL : http://nxt-firmware.ni.fr.eu.org/
* License : LOSLA, MPL
>That's belittled out non DM/DD people that are contributing too (and
>probably
>at the same level...) ;)
Then, obviously, they should apply for DM.
Seriously, I think we should stop begging for more. Valve's (subsidiary's)
offer is a very kind move and I'd not abuse that community attitude.
J
Hi there,
I think we all agree that the init system discussion is far away from
what is good for the project, under any political andsocial aspect.
I don't like systemd either, and I do not like the decision of the TC,
but what annoys me most is the attitude of some (too many) of my fellow
SysV s
partially fixed package was uploaded to unstable in January,
but was not unblocked, and
- is not in the package VCS
Could you please elaborate a bit on the state of Roundcube in Debian,
and what I (or others) could do to get it straight again?
Cheers,
Nik
--
Dominik George (1
Control: tags -1 + moreinfo
Hi,
> All browsers I have tried but Links2 crash constantly. Often they will not
> run at all.
Please provide more detail about this.
Which browsers did you try: How did you install and start them? What do
they output?
> I expect the browsers to work and not crash
Hi,
> Note that the problem still occurs on an available set of packages:
> just start with a Debian/stable system (jessie) and upgrade
> libgnutls-deb0-28 to unstable (no dependencies/conflicts will
> yield an upgrade of wget, which will occasionally segfault).
well, then, obviously, the depende
Package: general
Severity: normal
The Debian installer images for jessie apparently do not have watchdog
support enabled in the kernel, so they do not send heartbeats to the
BIOS.
This results in the installer system aborting and the machine resetting
after five minutes, or whatever the BIOS sees
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
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
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
>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
> > 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
> 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
> 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
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
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
>> 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
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 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
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
> 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
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
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
>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 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
> - 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
>> 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,
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 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
> >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
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
> > - 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
> - 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
> 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
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
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
> 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
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
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
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
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
-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
>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
>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
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
> 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
>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
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
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,
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
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,
> 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,
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
1 - 100 of 174 matches
Mail list logo
