On Sun, Jan 24, 2021 at 9:53 AM Leon Marz wrote:
> * New upstream version
I just filed a bug about this today, please close #980904.
--
bye,
pabs
https://wiki.debian.org/PaulWise
On Sat, Jan 23, 2021 at 3:30 PM Popout Apps wrote:
> A ready-made binary package is available here:
> https://github.com/PopoutApps/debian-popout3d
Debian requires source packages for sponsoring, please read through our intro:
https://mentors.debian.net/intro-maintainers
Git repositories should
On Wed, Jan 20, 2021 at 11:03 PM Chris wrote:
> This can be closed completely as there is now a Flatpak for this software.
Please see the documentation about how to close Debian bugs:
https://www.debian.org/Bugs/Developer#closing
PS: Flatpak is quite different and IMO not a substitute for a pro
On Sun, Jan 17, 2021 at 5:00 PM ransome wrote:
> My name is Robin, I am a long time Debian user and I would like to give
> something back by contributing an application I wrote to the Debian project.
Please take a look at our guide for new packagers:
https://mentors.debian.net/intro-maintainers
On Mon, Jan 4, 2021 at 5:21 PM Pali Rohár wrote:
>* New upstream release (Closes: #511059, #288455)
Please put these bug closings on separate lines and include some
descriptive information.
You may like to review the best practices for Debian changelog files:
https://www.debian.org/doc/manu
On Sun, Dec 27, 2020 at 11:17 PM Deepak Yadav wrote:
> I want to volunteer for contributing towards the Debian project. I did read
> the website but did not have a clear idea about where to ask for help and how
> to go about starting to contribute for a repository in Debian.
There are a lot of
On Fri, 2020-12-04 at 16:16 +0100, Romain Porte wrote:
> Version opentype-sanitizer_8.1.1+dfsg.1-1 uploaded to mentors.
Uploaded to NEW.
For future uploads please file an RFS again and I will get to it when I
am able to do so.
> Done, two warnings remain with `lintian -EviIL +pedantic`:
lintia
On Thu, Dec 3, 2020 at 1:09 PM Romain Porte wrote:
> Uploaded a new version +dfsg.1-1 on mentors with your explanation in
> debian/copyright as suggested by Lintian.
Here is a review of the package:
There do not appear to be any further issues that would block the upload.
So I am willing to spo
On Wed, Dec 2, 2020 at 11:45 AM Romain Porte wrote:
> dget -x
> https://mentors.debian.net/debian/pool/main/o/opentype-sanitizer/opentype-sanitizer_8.1.0-1.dsc
The package (and upstream) is missing copyright and license
information for all of the test fonts. Some of them contain no license
inf
On Mon, Nov 30, 2020 at 3:21 AM Benoît Rouits wrote:
> Thank you for the note. Lilypond is a command-line sheet music engraver
> similar (but different) to MusiXTeX. QAbc is a desktop user interface
> with an editor view and an SVG preview. The approaches are very
> different, IMHO. QAbc allow to
On Mon, Nov 30, 2020 at 12:48 AM Benoît Rouits wrote:
> QAbc has not yet an equivalent software in Debian. It's written in
> C++/Qt, uses libfluidsynth for synthesis, and makes use of abc2midi
> binary (from abcmidi package) to generate temporary midi files to be
> played. Thus, abcmidi has been p
On Wed, 2020-11-25 at 20:35 +0100, Marc Haber wrote:
> I am not sure how much of my packaging would need adapting to
> Config::Model to just use the copyright generation mechanism, so I'll
> probably stick with the busy work of hand-inspecting every single file.
I don't think CME places any requi
On Mon, Nov 23, 2020 at 10:26 PM Fabien Givors wrote:
>capbattleship - Sink your enemy before he gets you!
I would encourage you to use a more descriptive summary and also avoid
non-inclusive language. I think the summary you used in the ITP was
better for both of these suggestions.
--
bye,
On Fri, 2020-11-20 at 15:28 -0800, Jordan Justen wrote:
> It sound like you recommend incrementing the standards version and
> ignoring lintian, right?
Correct.
> As lintian helps to validate the package against the standards
> version, is there much benefit to updating the standards version
> b
On Fri, Nov 20, 2020 at 7:36 AM Jordan Justen wrote:
> This Standards-Version is not yet recognized by lintian.
When lintian is wrong about the Standards-Version being too new, it is
best to ignore it and wait until lintian is updated.
When lintian is wrong in general, file a bug report, unless
On Tue, 2020-11-17 at 09:58 +, Kasper Peeters wrote:
> I can of course use a Debian-specific toolset to do the installation,
> but that doesn't really solve my problem because it still leaves the
> same issues on other platforms. So at the moment my CMakeLists.txt
> contains a couple of ugly c
On Tue, Nov 17, 2020 at 8:47 AM Kasper Peeters wrote:
> Thanks to both, it's solved now.
The default tools should do that automatically, which ones are you
using and how did you solve it with them?
--
bye,
pabs
https://wiki.debian.org/PaulWise
On Mon, Nov 16, 2020 at 2:18 PM Kasper Peeters wrote:
> I am trying to package a program which contains a Python module. This
> module is not written in Python, but in C++/pybind11. It seems to me
> that the '.so' file this produces should go into an arch-dependent
> directory, e.g.
>
>/usr/li
On Fri, Nov 13, 2020 at 4:08 PM Marc Haber wrote:
> after a second look, licensecheck doesn't look too good any more. It
> doesn't grok the quite common SPDX notation, and I would love a tool
> that also checks debian/copyright (it's machine readable for a reason)
> and tells me which files are no
On Mon, Nov 9, 2020 at 8:49 PM Robin Gustafsson wrote:
> What's the recommended way to find such left-over files after an sbuild build?
You could hack something up by running git init+add+commit+status+diff
at the appropriate times in debian/rules. You would need to remove
that debugging before u
On Sat, Nov 7, 2020 at 8:06 PM Peter wrote:
> * License : GPL-2+, CC0-1.0, CC-BY-SA-3.0-US, Mayang-Free-Textures,
> FlashKit-Freeware
The FlashKit-Freeware license doesn't appear to allow modification or
distribution. The Mayang-Free-Textures license is quite poorly
drafted, doesn't expl
On Wed, Nov 4, 2020 at 2:29 PM Lorenzo wrote:
> Reading [1] it looks like you can list unsupported arch for autopkgtest in a
> new field of the control file,
> but i don't understand: how to do that?
According to the documentation linked from the announcement, the
Architecture field in debian/te
On Mon, Nov 2, 2020 at 4:39 PM Markus Demleitner wrote:
> And in particular, I suspect Debian distributes at least some of
> these logos somewhere already.
There appear to be fewer of them than I would have thought:
$ apt-file search ccbysa.png | wc -l
3
$ apt-file search ccby.png | wc -l
1
$ ap
On Thu, Oct 29, 2020 at 10:42 PM Lajos Veres wrote:
> Interestingly when I try to use lintian locally on a temp package, it does
> not say anything about the issues listed on the website:
> https://lintian.debian.org/sources/misspell-fixer/0.3-1.html
It is possible that the website used a differe
On Wed, Oct 28, 2020 at 11:30 PM Lajos Veres wrote:
> Do I understand well that practically the debian folder should have to
> disappear from the orig.tar.gz?
> Is this what the check verifies?
Correct.
> I am wondering to move the debian folder to a dedicated github
> repository to have it vers
On Fri, Oct 16, 2020 at 2:36 AM Mo Zhou wrote:
> What should be the next steps following our convention?
Since there is nothing using mkl-dnn (according to dak rm), just file
a removal request with `reportbug ftp.debian.org`.
$ ssh mirror.ftp-master.debian.org dak rm -s unstable -Rn mkl-dnn
Will
On Sat, 2020-10-03 at 10:11 +0200, Leon Marz wrote:
> Ok, no problem. asciidoc-base is now a metapackage, which depends on
> asciidoc.
Please also file a bug on nanoc so that you can eventually drop the
asciidoc-base transitional package.
I also suggest removing the suggests/recommends from asc
On Fri, 2020-10-02 at 16:13 +0200, Leon Marz wrote:
> I have uploaded a new version of the package with asciidoc-base back
> included, but as a duplicate of asciidoc. I hope this is alright.
I don't think it is appropriate to duplicate the package like that.
I would instead suggest either keepi
On Fri, Oct 2, 2020 at 12:48 PM Andrius Merkys wrote:
> On 2020-10-02 14:40, Leon Marz wrote:
> >* Remove vim-asciidoc (Closes: #954780)
> >* Remove asciidoc-base as it is unnecessary
> >* Put files from asciidoc-base to asciidoc
> >* Remove asciidoc-doc as there are no real docs
>
On Sun, Sep 27, 2020 at 3:18 PM Tobias Frost wrote:
> If upstream is gone and won't come back you can delete the watch file.
I suggest instead to keep the watch file, but add a comment mentioning
the upstream situation.
> Did you look if there are any forks that could be new upstream?
It can al
On Wed, Sep 23, 2020 at 7:40 AM Andreas Tille wrote:
> unfortunately upstream has not yet responded to this mail. My guess is
> that this is a general gcc-10 issue.
>
> Any hint how to solve this?
It looks like r-base-core is duplicating standard C types and defining
them incorrectly. If you edi
On Sun, Sep 20, 2020 at 10:50 PM Carlos Henrique Lima Melara wrote:
> I've been working in a package (QA) that show diff between documents. And a
> selling point is working with different encodings (see the long description
> bellow).
This feature is unfortunately quite hard to use, it seems like
On Sun, Sep 20, 2020 at 12:19 PM Lorenzo wrote:
> I'd like to check what can happen when i bump the debhelper compat level in
> dh-runit or some other dh extension:
> can i cause problem in a package that build-depends on dh-runit, but rely on
> a older (non compatibile) dh-compat level?
I'd su
On Sun, Sep 20, 2020 at 11:24 AM Heiko Schäfer wrote:
> I would have to sponsor something, but if over 1.5 years later nobody wants to
> sponsor it, I must accept that this tool seems to be an piece of utter
> bullshit.
The availability of a sponsor for software needing a sponsor is not
correlate
On Tue, Sep 15, 2020 at 3:46 PM Ryan Nowakowski wrote:
> If I install foo, which concrete package providing bar gets installed,
> blerg or blerg-plus? How can I control which concrete package(blerg or
> blerg-plus) gets installed when I install foo?
I think the best thing is for one of them to p
On Wed, 2020-09-09 at 15:00 -0400, Jeremiah C. Foster wrote:
> This sounds very useful - how can I follow along on the discussion? Is
> there a separate email list for this topic?
There is no discussion about using the snapshot API in the census, just
a FIXME item in the patches generation scrip
On Tue, Sep 8, 2020 at 1:32 AM Francisco M Neto wrote:
> I see a lot of RFS email that just sits there in the mailing list,
> without ever getting a response... is that normal?
It has always been the case that there are more people seeking
sponsors than available sponsors.
> Do responses about r
On Thu, Sep 3, 2020 at 2:56 PM Francisco M Neto wrote:
> I'd love to join! What do I do?
>
> I can (mostly) hold my own in those languages.
Great! I suggest you start by looking at the wiki pages I mentioned,
downloading the codebase and try running it locally. As I said the
bigge
On Thu, Sep 3, 2020 at 2:42 PM Sicelo wrote:
> This project sounds interesting, and I would like to avail myself to
> help/learn as much as possible. I know some basics in Python, SQL, and
> shell, but not Perl.
Great! The Perl parts are quite minimal (just for discovering RSS
feeds and downloadi
On Thu, 2020-09-03 at 14:12 -0400, Jeremiah C. Foster wrote:
> I would like to add that I've recently learned that the Derivatives
> Census can help determine programmatically the delta between Debian and
> a Derivative (if things are correctly configured.) For a distribution
> such as ours which
Hi all,
I'm looking for collaborators on the Debian derivatives census. The
census involves a mixture of social and technical work as well as
following different information feeds to find new Debian derivatives
and passing information to other Debian teams and folks.
https://wiki.debian.org/Deriv
On Mon, Aug 31, 2020 at 2:27 AM Francisco M Neto wrote:
> When I first opened reportbug it asked me against what package I wanted
> to submit the bug, and I hadn't noticed that it *should* have
> been sponsorship-requests; so it went somewhere else. I've sent email
> to control@b.d.o correcting th
On Sun, 2020-08-30 at 13:31 -0300, Francisco M Neto wrote:
> But I don't see my RFS here
I don't see your RFS on the BTS either:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?submitter=fmn...@fmneto.com
https://portfolio.debian.net/result?email=fmn...@fmneto.com
--
bye,
pabs
https://wiki.debi
On Sat, 2020-08-29 at 20:24 -0300, Francisco M Neto wrote:
> thanks for the reply. Do I have to send the RFS manually to
> this mailing list, or is it forwarded automatically? I made one with
> reportbug but I'm not sure if it was sent or not...
RFS that reach bugs.debian.org will automatically r
On Fri, Aug 28, 2020 at 3:50 PM Francisco M Neto wrote:
> I know how to use mentors.debian.org to make an RFS and ask for
> a sponsor. Is there a way to do that using a Salsa repository? Or do I
> just do it manually?
Some sponsors only sponsor Debian source packages (such as those
hosted
On Wed, Aug 19, 2020 at 11:04 AM Alistair J R Young wrote:
> I'm currently working on packaging a .NET Core utility for contrib
I note that .NET is Free Software these days, so you should be able to
package both for main instead of using contrib.
https://en.wikipedia.org/wiki/.NET_Core
https://g
On Sun, Aug 16, 2020 at 10:52 PM Joel Rivera wrote:
> I hope that some Debian mentor in this list could give me any guidance on how
> to move on given the current situation.
You could report Sam as MIA:
https://www.debian.org/doc/manuals/developers-reference/ch07.en.html#mia-qa
You could salva
On Mon, Aug 3, 2020 at 9:00 PM Ali Mezgani wrote:
> The package figure in the repository of Kali distribution.
> I don’t think that Debian security need it.
This is useful for sysadmins as well as pentesters so having it in
Debian is a good idea. Also Kali likes to contribute packages upstream
to
On Mon, Jul 20, 2020 at 3:07 PM François Mazen wrote:
> Is there special syntax in debian/changelog file to reopen such bugs?
> I would expect something similar to the (Closes: #123456):
> (Reopens: #123456)?
Excuse the terrible wrapping provided by my mail client, but I use this:
export pkg=pho
On Sun, Jul 19, 2020 at 3:31 PM François Mazen wrote:
> I'm trying to reintroduce the photoprint package [1],
Please note the extra steps required when reintroducing packages,
particularly the requirement to reopen and triage the bugs closed by
the removal.
https://www.debian.org/doc/manuals/dev
On Fri, Jul 10, 2020 at 11:33 AM Boian Bonev wrote:
> I think that most of the things are fixed now, please proceed with your
> review/upload.
Will do so in the next days.
> I was surprised that packaging the program is comparable to the program
> creation itself; for some reason I had expectati
On Thu, Jul 9, 2020 at 1:52 PM Dmitry Baryshev wrote:
> I have a cmake-based project and Debian rules. The rules build 5 deb
> packages. One of the packages is just a set of .so plugins w/o any libraries
> or executables.
>
> The Debian build system peeks the main project's version for this part
On Wed, 2020-07-08 at 20:09 +0300, Boian Bonev wrote:
> Checking further I see that in order to enable this protection, a -Wl,-
> z,now needs to be added to LDFLAGS and dpkg-buildflags does not include
> it (at least on my sid install). For the sake of test, I have added it
> in Makefile and the w
On Sun, Jun 28, 2020 at 2:36 AM Boian Bonev wrote:
> iotop-c - simple top-like I/O monitor (implemented in C)
I am willing to sponsor this.
Some issues that I think need to be fixed before uploading:
Please comply with Debian Policy about build verbosity:
https://www.debian.org/doc/debian-po
On Thu, 2020-06-11 at 02:53 -0400, Qianqian Fang wrote:
> that's possible. however, some of the file release systems, such as
> MATLAB File Exchange, only links to the github generated
> master.zip/release packages. if I remove the mex files from my github
> folder, users will not be able to run u
On Thu, 2020-06-11 at 01:52 -0400, Qianqian Fang wrote:
> I listed zlib1g in the Depends section, isn't it the provider of libz.so?
The Depends in debian/control are not the same as the dependencies of
the library file itself (although usually the library dependencies are
automatically translated
On Wed, Jun 10, 2020 at 8:25 PM Qianqian Fang wrote:
> dpkg-shlibdeps: warning: symbol deflateBound used by
> debian/libzmat1/usr/lib/x86_64-linux-gnu/libzmat.so.1 found in none of the
> libraries
>
> although, I've already added zlib1g-dev to Build-Depends and zlib1g to the
> Depends fields, I
On Mon, Jun 1, 2020 at 3:04 PM The Wanderer wrote:
> If I need to compile a program to run in an environment where I can't
> know what libraries / library versions are going to be available, or
> maybe even do know for a fact that certain ones will not be available,
> the obvious solution is to li
On Mon, 2020-06-01 at 14:18 +, Vasyl Gello wrote:
> So static libs present in packages like popt are remnants of the past
> and the general practice now is to discourage shipping all kinds of
> static libraries unless it is Go/OCaml… as mentioned in this wiki
> page?
Right.
--
bye,
pabs
h
On Mon, Jun 1, 2020 at 1:42 PM Vasyl Gello wrote:
> I often link software statically, especially targeting Android.
> So I guess keeping static library won't hurt as part of -dev
> package.
Where dynamic libraries are available there are usually only downsides
to static libraries, in Debian we tr
On Thu, May 28, 2020 at 6:33 PM Roland Plüss wrote:
> What path do you think should I choose to be best conform with Debian?
I would package the games into Debian packages so that the source
data/code is available and built by the Debian packaging, using paths
something like /usr/share/dlauncher/
On Thu, May 28, 2020 at 3:27 PM Joachim Bauernberger wrote:
> I've created an ITP[1] and am looking for some guidance on putting this
> package[2] into sid.
Check out our guide and especially the RFS (request for sponsor) howto:
https://mentors.debian.net/intro-maintainers
https://mentors.debia
On Mon, May 25, 2020 at 10:25 PM Alexis Murzeau wrote:
> To: Debian Mentors List
This would have been more on-topic on the debian-popcon list.
> Is there a page that shows a popcon graph with each Debian suites for a
> given package ?
popcon does not report package versions, so this isn't real
On Mon, May 18, 2020 at 3:43 PM Christoph Biedl wrote:
> | Architecture: linux-all
>
> but there is no such architecture wildcard.
You cannot make this an architecture wildcard, because wildcards
resolve to real architectures in the .deb, which would still be
Architecture: all, which means dak wo
On Thu, 2020-05-07 at 08:44 -0400, Kyle Edwards wrote:
> * Putting different CMake install components into different binary
> packages (for example, putting the "Libraries" component into
> libexample and the "Development" component into libexample-dev), which
> is easier than listing individual f
On Tue, Apr 28, 2020 at 8:57 PM Kyle Edwards wrote:
> It builds those binary packages:
>
> dh-cmake - Debhelper programs for CMake projects
How is this different to the existing cmake support in debhelper?
$ dpkg -L debhelper libdebhelper-perl | grep -i cmake
/usr/share/perl5/Debian/Debhelpe
On Tue, Apr 21, 2020 at 5:29 AM wrote:
> Instead, I would like to build libfreehep-graphicsio-*-java binary
> packages from the single source package, and remove the old source
> packages. However, I am not sure if two source packages producing binary
> packages with the same names will not confl
On Wed, Apr 22, 2020 at 3:14 PM Aaron Boxer wrote:
> I have created a new package for a library (grok)
This is a very generic name, I think it would be best to rename the
upstream project so that other distros packaging the other grok don't
also run into this issue.
--
bye,
pabs
https://wiki.de
On Fri, Apr 3, 2020 at 9:03 PM Scott Talbert wrote:
> Unless I'm missing something, there's no way to patch a binary file (e.g.,
> an image file) with quilt, correct? Any workarounds?
Which package, binary file and changes to it are we talking about?
Some actions in decreasing order of preferen
On Thu, Mar 5, 2020 at 2:54 PM Mathieu Malaterre wrote:
> Could someone please point me to an example d/control where
> sse4.2-support is used ?
Use of this is usually a workaround for flaws in the software, it is
much better to fix the software instead. The right way to support SSE
4.2 is to cho
On Tue, 2020-01-28 at 16:00 -0500, Sanford Rockowitz wrote:
> GProbe is the proprietary Genesis protocol.
Is there a list of proprietary extensions to DDC somewhere?
I wonder how useful implementations of these would be.
For GProbe support for it could be used to start an open source monitor
fi
On Mon, Jan 27, 2020 at 4:50 PM Sanford Rockowitz wrote:
> True. ddcutil internals were reworked some time ago for what I call User
> Supplied Feature Definitions.
Another aspect of manufacturer-specific features is that they can be
used to do things that never should be allowed, like run arbitra
On Mon, 2020-01-27 at 03:28 -0500, Sanford Rockowitz wrote:
> ddcui is not in Debian because, simply put, it's not ready for prime time.
Fair enough, I'll be glad to try it when it is.
> My question to the list was whether this is acceptable, which it
> appears to be.
Correct.
> If you're curi
On Sun, 2020-01-26 at 23:01 -0500, Sanford Rockowitz wrote:
> I'm unaware of plans to support DDC in the Linux kernel.
I just discovered the ddcci-driver-linux project. It is available in
Debian in the ddcci-dkms binary package. I've tried it locally but it
doesn't appear to be very useful for me
On Sat, Jan 25, 2020 at 11:13 PM Sanford Rockowitz wrote:
> What's unusual is that the command line version does not depend on the
> shared library. Both versions are built from the same source package
...
> Is this design just atypical, or does it violate Debian practice in some
> way?
It is ha
On Fri, Jan 17, 2020 at 3:56 AM Chew, Kean Ho wrote:
> On Fri, Jan 17, 2020 at 11:25 AM Paul Wise wrote:
>
> > For future simple-cdd questions I suggest contacting the simple-cdd
> > maintainer about this, most folks on this list aren't simple-cdd users
> > (
On Fri, Jan 17, 2020 at 2:24 AM Chew, Kean Ho wrote:
> is SDDM package not expected to get installed during base system setup phase
> in a simple-cdd built Debian ISO OS installation?
For future simple-cdd questions I suggest contacting the simple-cdd
maintainer about this, most folks on this lis
On Sat, Jan 4, 2020 at 5:10 PM Tong Sun wrote:
> How to delete my package from ftp.upload.debian.org?
Usually that means using dcut (from devscripts), but in this case the
package is no longer in the upload queue so you cannot remove it from
there.
>
> Package has already been uploaded
On Thu, Jan 2, 2020 at 6:09 AM Hsieh-Tseng Shen wrote:
> Moreover, I'd like to take over this package but I'm not sure if I have
> to solve some bugs or just by changing debian/control. Btw, I already
> asked maintainer for this from https://bugs.debian.org/945185.
The O in the title of this bug
On Thu, Jan 2, 2020 at 4:33 AM ansimita wrote:
> I'd like to try my hand at Debian's Infrastructure Projects.
I'm not entirely clear what you mean by Infrastructure Projects, you
could mean core distribution projects like apt and dpkg or you could
mean some of Debian's services:
https://wiki.deb
> From: Adam Borowski
> While I agree with remarks about proliferation of similar tools, it is not a
> reason to stop new development. As your tool can fix the problems, it's
> interesting.
FYI codespell can also fix problems using the -w option.
--
bye,
pabs
https://wiki.debian.org/PaulWise
On Sun, Dec 22, 2019 at 7:42 PM Jörg Frings-Fürst wrote:
> I use now /usr/sbin/dmidecode -V. Uploaded to mentors and into git.
Things like that should be marked as trivial autopkgtests:
https://lists.debian.org/msgid-search/8b000c23ac2defbfeea7d5a0bc28ec2e3df55baa.ca...@debian.org
--
bye,
pabs
On Fri, Dec 20, 2019 at 2:47 AM Tong Sun wrote:
> If I'm updating a package that I maintain. I shall just do it.
> I.e., there isn't any BTS (like ITP) to file and to close, right?
If you have upload privileges for the package then you can just
upload. If you don't then you will need to file an R
On Tue, 2019-12-17 at 19:25 +0800, Chew, Kean Ho wrote:
> Will cryptsetup picks up Adiantum availability once I enabled in kernel?
Sounds like the answer is yes according to the manual page:
https://manpages.debian.org/buster/cryptsetup-bin/cryptsetup.8.en.html#NOTES_ON_SUPPORTED_CIPHERS,_MODES,
On Tue, Dec 17, 2019 at 8:30 AM Chew, Kean Ho wrote:
> Is there any successful Adiantum disk encryption for
> amd64 pc/laptop implementation?
As I understand it, Adiantum is supposed to be for low-end Android
phones that can't do better encryption. Debian does not ship a Linux
kernel on amd64 tha
On Sat, Dec 7, 2019 at 9:36 PM Dan Davison wrote:
> Currently (FreeBSD, Rust Cargo, Arch Linux, Homebrew) the package name is
> "git-delta", which installs an executable named "delta". Can it do the same
> for Debian?
There is one package already using that executable name:
$ apt-file search b
On Fri, Dec 6, 2019 at 11:12 PM Rebecca N. Palmer wrote:
> However, before entering the chroot, it tries to run debian/rules clean
> *outside* the chroot; in some cases the clean step needs some of the
> build dependencies, so this can fail.
There is the --use-pdebuild-internal option to do this
On Fri, Nov 22, 2019 at 9:44 PM Wookey wrote:
> No, the compat file should match the dependency, and determines the
> actual behaviour of debhelper in the packaging. i.e. that's the
> important bit, and the control file dependency is just being set to
> match.
BTW, to avoid the possibility of mis
On Mon, Nov 4, 2019 at 2:28 PM Shengjing Zhu wrote:
> On Mon, Nov 4, 2019 at 5:18 AM Adam Borowski wrote:
> > On Sun, Nov 03, 2019 at 04:27:12PM +, Mo Zhou wrote:
> >
> > No check for AVX yet, but a quick hack that may be useful to you is attached
> > to: https://lists.debian.org/debian-devel/2
On Sun, 2019-11-03 at 10:21 +0800, Holloway Kean Ho wrote:
> I'm restricted due to git version control service providers.
Sounds like you need to use a generic web hosting provider instead,
then you can generate your apt repository locally and sync all the
repository files over to the hosting pro
On Sun, 2019-11-03 at 09:57 +0800, Holloway Kean Ho wrote:
> I'm getting restricted to only using Hugo.io.
It is unlikely that a blog engine will be able to generate an apt
repository. Could you say more about the restriction?
> Is there a documentation (or spec) that mentions about how "apt"
>
On Sun, Nov 3, 2019 at 8:51 AM Holloway Kean Ho wrote:
> Curiously, is it possible to host a deb server using Hugo.io where apt can
> seek
> a given URL to get updates? (enabling for "apt-get update / upgrade")
>
> I'm looking at customizing the generation process onto Hugo.io so we need not
> to
On Wed, Oct 30, 2019 at 5:03 AM Stephen Kitt wrote:
> I’ve pushed that to the games-team repository, and tagged the release. Please
> register a guest account on Salsa if you don’t already have one:
> https://signup.salsa.debian.org/
> Then you’ll be able to request access to the cowsay repository
On Wed, Oct 23, 2019 at 1:23 PM Elfyn McBratney wrote:
> Ahh, that is good news. Glad to have been wrong. I'll send him an e-mail
> via one of those addresses and I'll be sure to mention the mail-disable thing.
FYI, Al updated rasdaemon today :)
--
bye,
pabs
https://wiki.debian.org/PaulWise
On Wed, Oct 23, 2019 at 8:47 AM Francis M wrote:
> I sent an e-mail to Al Stone (ahs3@d.o) who's listed as rasdaemon's maintainer
> on packages.d.o and, after a confusing interraction with Debian's SMTP server
> which responded to his address with "550 ", I discovered
> that his account has been r
On Tue, Oct 15, 2019 at 4:06 PM Paul wrote:
> Rather than starting work on version 1.23 I am thinking I will open
> source my project and get it bundled with Debian. I would appreciate
> some advice on how I should proceed. I have been reading
> https://www.debian.org/doc/manuals/developers-refere
On Wed, 2019-10-02 at 19:20 +0200, Mathieu Malaterre wrote:
> Very very odd. Seems to be a server side issue.
...
> gpg: key 421EE936326AC15B: new key but contains no user ID - skipped
...
> Donno what is wrong with https://keys.openpgp.org:443
It doesn't distribute UIDs without permission of the
On Tue, Oct 1, 2019 at 3:00 PM Mathieu Malaterre wrote:
> gpgv: Signature made Wed 31 Jul 2019 10:01:53 AM CEST
> gpgv:using RSA key 3BCC43D4D2C87D1784B69EE4421EE936326AC15B
> gpgv: Can't check signature: No public key
Sounds like the key that has signed the tarball is not availab
On Sun, Sep 8, 2019 at 9:51 PM Yangfl wrote:
> https://www.debian.org/doc/debian-policy/ch-opersys.html says "The
> default behaviour is to enable autostarting your package’s daemon",
> IIUC.
Apologies for not making it clear but my message was about the
situation where a daemon needs configurati
On Wed, Sep 4, 2019 at 7:57 AM Adam Borowski wrote:
> If there's no reasonable default setup, then an error message should at
> least say the config is missing.
In addition the default sysvinit/systemd setup should be that the
service should be disabled by default until the admin enables it, IIRC
101 - 200 of 2570 matches
Mail list logo
