On Sun, 2020-11-01 at 14:56 -0800, Russ Allbery wrote:
> Utkarsh Gupta writes:
>
> > That said, it'd be a bit weird if they don't report these issues and ask
> > for a CVE assignment against these. Anyway, the security team might
> > know more about this.
>
> It appears to be the output of auto
On Sun, 2020-11-08 at 22:41 +0100, Jérémy Lal wrote:
> Using toy story names for debian releases surely isn't free from any
> Debian/pixar license ?
> Or is it ?
IANAL either, but I did a research project on IP law in the US, and our
usage of the names are almost certainly fine, as explained by Pa
On Tue, 2020-11-10 at 10:07 +, Simon McVittie wrote:
> On Tue, 10 Nov 2020 at 10:45:07 +0100, Johannes Schauer wrote:
> > I'm confused. We are packaging libraries of language X but then those
> > packages
> > will not be used by people who write software for language X on
> > Debian?
> > Intuit
Hi all,
I just wanted to note the breakage, and ask for an NMU. I have prepared
and uploaded a patch, both to Salsa and to the BTS, and it has been a few
days without any response. The patch is very simple: just replace all
occurences of isAlive() with is_alive(), and the package works. I am not
On Wed, 2020-12-09 at 23:12 +0500, Andrey Rahmatullin wrote:
> On Wed, Dec 09, 2020 at 12:52:30PM -0500, Calum McConnell wrote:
> > Hi all,
> > I just wanted to note the breakage, and ask for an NMU. I have
> > prepared
> > and uploaded a patch, both to Salsa and to
Hi all,
As someone who runs amd64/i386 multiarch, this statement from Adrian:
> i386 hardware is so numerous and widely spread, that every tiny fraction
> of i386 users might be more users than half of our release architectures
> combined. It is not even clear whether this is just an exaggeration
On Mon, 2020-12-14 at 10:02 -0800, Russ Allbery wrote:
> One possible intermediate option shy of dropping the i386 architecture
> would be to drop the i386 kernel and instead help all i386 installs
> switch
> to the amd64 kernel while still running i386 binaries. (That said, this
> will obviously
On Mon, 2020-12-14 at 14:54 -0800, Russ Allbery wrote:
> Calum McConnell writes:
> > The point I'm making is that i386 processors are still incredibly
> > common, and we shouldn't abandon their users.
>
> Not abandoning users is a powerful motivating force, b
On Wed, 2020-12-16 at 19:06 +0100, John Paul Adrian Glaubitz wrote:
> Hi!
>
> For some reason, apt is ignoring the "check-valid-until" flag for me, no
> matter whether
> I'm passing that option in /etc/apt/sources.list or on the command line
> (see below).
>
> Does anyone have any idea what I'm m
I spent so long fiddling with my chroot to try and find a repoistory with
an invalid release file but a valid key (I was looking in
archives.debian.org, not realizing that the valid-until field didn't exist
for any of them!), that it seems Paul has beaten me to the punch.
Whoops.
Calum
signatur
On Fri, 2020-12-18 at 01:15 +, Paul Wise wrote:
> On Thu, Dec 17, 2020 at 10:03 AM Ansgar wrote:
>
> > (Bonus points if this keeps the original signature if possible.)
>
> Two separate signatures is possible for Release+Release.gpg, just
> rename the latter to .old, but what can you do fo
On Fri, 2020-12-18 at 14:11 +0200, Adrian Bunk wrote:
> On Fri, Dec 18, 2020 at 09:11:42AM +0100, Raphael Hertzog wrote:
> > On the top of my head:
> > - as a user, I like to have to only know about "apt/dpkg" instead
> > of pip/npm/gem/...
>
> This sounds as if you are making the case for a hig
On Tue, 2020-12-22 at 21:34 +0100, Richard wrote:
> why no respond >:
Sir,
This is a volunteer organization. Anyone and everyone here contributes
soley because they feel like it. You have not paid us anything,
therefore, we are not beholden to give you anything. That includes a
response to your
On Thu, 2021-01-21 at 11:18 -0700, Lou Poppler wrote:
> On Thu, 2021-01-21 at 11:06 -0500, SDA wrote:
> > On Thu, Jan 21, 2021 at 08:55:10AM -0700, Lou Poppler wrote:
> > > >
> > > > Got them from this url:
> > > >
> > > > https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firm
You may have noticed that you didn't get any responses. Your message was
caught by my spamfilter, and was furthermore not very clear.
As for your error, it seems likely that there is an error with the
internet connection. Why and how I cannot tell you, as there is not
enough information
signat
down to "we're letting packages treat the folders as separate, but in
the layout they aren't". Since we are already changing dpkg to make it
treat the folders as equivalent (which we need to do to avoid a long and
painful upgrade cycle), why not just save a few hundred symlinks an
On Wed, 2021-08-11 at 00:51 +, Paul Wise wrote:
> On Tue, Aug 10, 2021 at 5:38 PM Andrey Rahmatullin wrote:
>
> > "So, Arch Linux, one of the main reasons, there's a couple, but the
> > main
> > reason is the rolling updates of Arch allows us to have more rapid
> > development for SteamOS 3.0,
On Fri, 2021-08-20 at 11:03 +0800, YunQiang Su wrote:
> Paul Wise 于2021年8月20日周五 上午10:50写道：
> >
> > On Thu, Aug 19, 2021 at 9:17 PM Boyuan Yang wrote:
> >
> > > So we will have https://salsa.debian.org/debian/which-gnu providing
> > > a binary
> > > package with name "which". I will upload it to
Package: wnpp
Severity: wishlist
Owner: Calum McConnell
* Package name: bitwarden
Version : 1.17.2
* URL : http://www.bitwarden.com/
* License : GPL-3
Programming Lang: Typescript
Description : fully open-source, cross-platform password manager
== Long
> > > I kinda like the idea of prefixing *all* temporary directory with
> > > a '_'
> > Completely reasonable and almost auto-explaining, I'd say. +1 for
> > Michael's suggestion.
>
> What about placing temporaries below debian/build/? Anything where
> names
> aren't fixed in Policy, i.e. which co
Package: wnpp
Severity: wishlist
Owner: Calum McConnell
X-Debbugs-Cc: debian-devel@lists.debian.org, calumlikesapple...@gmail.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
* Package name: whitakers-words
Version : 0~20.6.7
Upstream Author : Martin Keegan
* URL
21 matches
Mail list logo
