On Sun, 2024-02-11 at 17:04 -0500, Darren Tomblin wrote:
> I’m wondering what I have to do to say I want to work on a bug
Which bug report are you looking at?
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
On Wed, 2023-09-27 at 21:21 +0200, Niels Thykier wrote:
> Turns out a give-back is not sufficient (wrong state). Seems like you
> will need to find a buildd admin. Try debian-wb-t...@lists.debian.org or
> loon...@buildd.debian.org
The folks on #debian-ports said it needs a maintainer upload
On Mon, 2023-09-18 at 12:51 +0100, Peter Blackman wrote:
> Is anyone aware of an equivalent package?
There are many tools in this area:
https://wiki.debian.org/CopyrightReviewTools
Probably the best one is scancode-toolkit, but it isn't in Debian.
--
bye,
pabs
On Sun, 2023-08-13 at 11:51 +, John Scott wrote:
> Because carl9170 is largely under the GPL and we're obligated to
> distribute complete sources for our binaries, I've set Static-Built-
> Using on both gcc (because of libgcc) and Newlib.
FYI, that wasn't the correct thing to do.
On Wed, 2023-07-12 at 06:49 +, Sune Vuorela wrote:
> Either you need to do a packagename change (and debian specific SONAME
> iwth all that entails; or maybe there is a way to restore the old abi.
> Can you provide a full diff of header,implementation of the relevant
> classes ?
You can also
On Mon, 2023-06-19 at 14:40 +0200, Alec Leamas wrote:
> Anyone which can shed some light on the bookworm-backports status and
> perhaps also where my upload ended up?
I suggest checking the debian-backports mailing list archives and
if the answer isn't there, ask on the list or on the IRC
On Tue, 2023-06-13 at 16:48 +0200, Daniel Gröber wrote:
> I'm working on packaging prjtrellis[1] which has a git submodule that is
> required for building. My plan is to use dpkg-source's multi upstream
> tarball support to do this.
This appears to be the repo of the submodule:
On Tue, 2023-06-13 at 19:22 +0200, Oliver Reiche wrote:
> 1. Due to the missing build description, is it ok if the maintainer
> provides a Makefile for building the C++ libraries in ./debian?
...
> 4. Such a Makefile (and control file) will be quite lengthy.
The upstream repo seems to use bazel
On Tue, 2023-05-30 at 21:41 +0200, Michael Ablassmeier wrote:
> trurl (0.7-1) unstable; urgency=medium
> .
> * New upstream release.
Uploaded.
Upstream has added -Werror to the default CFLAGS. It isn't recommended
to do this in released software, because it means a lot more build
failures
On Wed, 2023-05-17 at 22:10 +0200, Michael Ablassmeier wrote:
> I am looking for a sponsor for my package
> "libwebservice-musicbrainz-perl":
I suggest moving your Perl packages into the Perl team.
You'll get shared maintenance and sponsorship when needed.
--
bye,
pabs
On Mon, 2023-05-15 at 18:14 +0200, Oliver Reiche wrote:
> Could you please tell me if it is acceptable for Debian that I have
> build dependencies (proto files) in ./debian/third_party, with the
> copyright file explicity mentioning those?
Generally all build dependencies should be packaged
On Mon, 2023-04-24 at 13:54 -0700, Soren Stoutner wrote:
> It is a pleasure to make the acquaintance with a fellow developer
> working on packaging a browser based on Qt WebEngine.
The docs suggest WebKitGTK, QT WebEngine support is experimental.
https://github.com/atlas-engineer/nyxt/
Nyxt
On Mon, 2023-04-17 at 18:02 +0200, Alec Leamas wrote:
> Hence I need to use the backports. I see no particular problem with
> backporting 5.8.0 from sid/testing once it's there to bookworm-backports.
This can only happen after it reaches testing, so after the bookworm
release after testing
Control: close -1
On Sat, 2023-04-15 at 15:59 +0200, Michael Ablassmeier wrote:
> I am looking for a sponsor for my package "trurl":
What is the status of getting your new OpenPGP key accepted? Some links
related to that below, if you are having trouble with keysigning then
key endorsements
On Sat, 2023-04-01 at 20:27 -0700, Bryan Gardiner wrote:
> ... sponsor to help me reintroduce "tagainijisho" into Debian:
Please note the extra steps needed when reintroducing packages:
https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#reintroducing-packages
--
bye,
pabs
On Tue, 2023-03-14 at 18:41 -0700, Soren Stoutner wrote:
> I am one of the Debian Qt WebEngine maintainers, and I also submit
> code to the upstream Qt project.
>
> The Salsa link you included appears to be a bit misinformed about
> security support for Qt WebEngine in Debian.
I was just
On Sat, 2023-03-11 at 14:41 -0700, Soren Stoutner wrote:
> * URL : https://www.stoutner.com/privacy-browser-pc/
> privacybrowser - web browser that respects your privacy
I note that this browser depends on Qt WebEngine, all the Qt based web
engines are not security supported in
On Wed, 2022-11-09 at 13:47 +0100, Mathieu Malaterre wrote:
> I see that jpeg-xl test suite is running of out time hurd-i386:
> What would be the "right" way to disable the test in d/rules ?
I suggest instead trying to debug it on the porterbox where there is no
sbuild based timeout to contend
On Sat, 2022-11-05 at 01:44 +0100, Alexandre Detiste wrote:
> So this will be 0.9.48.
Please upload a source package to mentors.debian.net or elsewhere
and I will review and upload the package including dh-cruft.
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This
On Sat, 2022-10-22 at 15:59 +0200, Fabio Fantoni wrote:
> Which would be the best tool(s) to get a good starting debian/copyright
> and decrease the time it takes to complete and fix it?
Allegedly scancode is the best option for that, but it isn't in Debian.
I think decopy/licensecheck are the
On Fri, 2022-10-21 at 17:29 +0200, Robin Alexander wrote:
> 1. Why didn't the "source-is-missing" error show on my environment
> (prior to push the package with dput)? Is there a specific lintian setup
> that I missed? FYI, my packaging environment runs on bullseye (I tried
> sid yesterday,
On Thu, 2022-10-20 at 14:42 +0200, Robin Alexander wrote:
> I should have written instead that the upstream odr-audioenc *INCLUDES
> MODIFIED SOURCES* of fdk-aac (Fraunhofer FDK AAC Codec Library for
> Android). Since the original version of the Fraunhofer FDK AAC Codec
> Library for Android
On Wed, 2022-10-19 at 10:26 +0200, Robin Alexander wrote:
> My package odr-audioenc was rejected after it reached the NEW queue
> because one of the library it depends on does not belong to "main" but
> to "non-free". I therefore need to change the section in file
> debian/control from
On Thu, 2022-10-06 at 09:18 +0200, Tobias Frost wrote:
> Oh, sorry; I missed that you meant d/test/control…
> (Though, Reading [1], I'm not sure if there is support for "!", but I
> guess it is worth a try…)
elbrus confirmed on #debci that ! is supported in d/t/c Architecture.
--
bye,
pabs
On Thu, 2022-10-06 at 07:15 +0800, Paul Wise wrote:
> On Tue, 2022-10-04 at 08:50 +0200, Mathieu Malaterre wrote:
>
> > Is there a way to de-activate explicitly s390x from the default
> > autpkgtest list ?
>
> I asked about this #debci on IRC and got this answer:
M
On Tue, 2022-10-04 at 08:50 +0200, Mathieu Malaterre wrote:
> Is there a way to de-activate explicitly s390x from the default
> autpkgtest list ?
I asked about this #debci on IRC and got this answer:
pabs: haven't checked but the answer normally is that the
package also builds arch:all
On Wed, 2022-09-21 at 10:44 +0100, Sam Morris wrote:
> It looks like the connection's being closed during the transfer;
If you are able to try the upload from a different Internet connection,
or with a VPN or via Tor that might help narrow down the issue.
> dput-ng's error handling could
On Fri, 2022-09-16 at 19:53 +0200, Fab Stz wrote:
> How does is this actually managed on the official buildd servers? How
> does it actually know which DEB_BUILD_PROFILES to apply on each run?
The Debian buildds currently do not have support for build profiles,
for now build profiles are only
On Mon, 2022-09-12 at 10:05 -0400, Aaron Boxer wrote:
> My codec project uses SIMD code for x86 and AArch64 architectures.
> Also, as there are different versions of SIMD i.e. SSE vs AVX vs
> AVX2, the project uses a library that builds multiple versions of the
> accelerated code and chooses
On Sun, 2022-09-11 at 21:40 +0200, Philippe SWARTVAGHER wrote:
> Upstream has several files describing copyrights of the project [1-4].
> In d/copyright, I licensed the whole project with Apache 2.0, with
> "Google Inc." as copyright holder. Should I detail more?
Generally, the ftp-masters
On Tue, 2022-08-30 at 03:56 -0400, Matt Arnold wrote:
> Guidance for returning contributors
We unfortunately don't have a general guide on this topic, but it might
be worth writing one if you are keeping notes on the process.
> My question is how would i now contribute this back?
Every team is
On Mon, 2022-08-22 at 21:00 +0200, Fab Stz wrote:
> Does there exist a tool for Debian that will parse a package directory (its
> source files), extract the "SPDX-License-Identifier:" and produce something
> that would fit into a machine-readable debian/copyright file?
For the more general
On Sat, 2022-08-13 at 11:31 +0200, Marc Haber wrote:
> I think this is worth doing only if the number of your reverse depends
> is well in the two-digit range or above that. That doesn't apply (yet)
> to gensio, so I'm likely to remove the symbols file from my package
> again and override the
On Sat, 2022-08-13 at 22:19 +0200, Marc Haber wrote:
> dpkg-gensymbols does not seem to be willing to grok the second line
> ("gensio_log_levels, not a valid version").
>
> Also, the arch extension does not seem to be in deb-symbols(5).
See the deb-src-symbols(5) manual page, I think you want
On Fri, 2022-08-12 at 23:35 -0500, Michel Alexandre Salim wrote:
> -O2 is baked into the Makefile. The last option should win so -O0 takes
> precedence, I suppose? I can probably convince upstream to implement a
> simple ./configure.
Sounds right, so probably not an issue, just seemed a bit
On Fri, 2022-08-12 at 12:06 +0200, Marc Haber wrote:
> what's the benefit in having a symbols file?
It means that packages depending on a library can relax their version
dependencies on that library to the oldest version that supports all
the symbols they use. Until the symbols mechanism was
On Fri, 2022-08-12 at 07:00 +0200, Tobias Frost wrote:
> ${shlibs:Depends}
I mean for the library, what do you set debian/$package.shlibs to?
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
On Thu, 2022-08-11 at 16:10 +0200, Tobias Frost wrote:
> I tried them on a few occasions only to drop them a few uploads later, as
> they add a lot of maintainance burden. They will frequently break, as some
> other package or toolchain might have influences, are
> architecture dependent and once
On Thu, 2022-08-04 at 14:53 -0500, Michel Alexandre Salim wrote:
> Saw that from the notes you gave to the initial upload too. I checked
> libsystemd.pc and... there's nothing we can use there, unfortunately.
How about this?
pkg-config --variable systemd_user_unit_dir systemd
--
bye,
pabs
On Thu, 2022-07-21 at 10:30 +0200, Marc Haber wrote:
> Is there also a documented way to install the packages from stable,
> testing, unstable to automatically test updates?
That sounds like what piuparts is for:
https://packages.debian.org/unstable/piuparts
https://piuparts.debian.org/
--
On Fri, 2022-07-15 at 00:32 +0200, Alec Leamas wrote:
> Any clues out there?
The Debian mentors site only verifies against the OpenPGP keys that
have been registered on the mentors site for each individual user.
So login to your mentors account, update the key there and reupload.
If you still
On Thu, 2022-07-14 at 17:49 -0400, Matt Barry wrote:
> I imagine I'm missing something simple wrt pbuilder.. any ideas where
> to look?
Are you getting any errors from the pbuilder update command?
Are you updating the same chroot as you are building with?
You can also add a hook that does apt
On Thu, 2022-07-14 at 09:52 +0200, Marc Haber wrote:
> How would I do that in autopkgtest? Can I uninstall and reinstall the
> package in question while an autopkgtest is running?
Sounds like you want the breaks-testbed and needs-root restrictions:
On Thu, 2022-06-09 at 08:38 +0200, Marc Haber wrote:
> I havent looked at the test in detail, I have not yet decided whether
> the package would be helpful in Debian. It looks like the test has
> en_GB.UTF-8 hardcoded, sets the locale to that value and then fails
> it it's not there. Most likely
On Thu, 2022-06-09 at 07:28 +0200, Marc Haber wrote:
> I am working on a package written in python that thankfully has a
> test suite. Unfortunately, one of the tests fails if the en_GB.UTF-8
> locale is not present.
Any idea why the test requires that locale? Tried C.UTF-8?
> How do I solve
On Wed, 2022-06-01 at 01:41 +0200, Bastian Germann wrote:
> On reintroducing a package you need to file an ITP on wnpp as well.
Please note there are some extra steps in addition to filing the ITP:
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#reintroducing-pkgs
--
bye,
On Tue, 2022-05-31 at 18:17 +0800, starcold14 wrote:
> How to install kdump in debian11?
I answered this question on debian-devel too. In future, please don't
send the same question to multiple lists and please send questions
about using Debian to our support channels instead of other lists.
On Tue, 2022-05-17 at 20:40 +0100, Dave Ewart wrote:
> Should I create RFS? I'm unclear whether this is more suited to a
> one-off upload or for ongoing maintainership. Advice welcome!
It depends on the sponsor, some prefer you to file a public RFS for
each upload, others prefer you to contact
On Mon, 2022-05-09 at 20:18 -0700, Michel Alexandre Salim wrote:
> I am looking for a sponsor for my package "psi-notify":
I prefer that three issues are fixed before uploading psi-notify:
Since the package requires Linux kernel PSI APIs, it probably won't
work on kFreeBSD or Hurd, if so,
On Wed, 2022-04-06 at 16:26 +, Eivind Naess wrote:
> The project is using ./autogen.sh to generate the configure scripts,
> et al for the project. When I got to tag and create a release, I have
> to upload the resulting tarball with the resulting configure scripts
> embedded.
Personally I
On Thu, 2022-03-03 at 16:30 +0100, Albert van der Horst wrote:
> Is it frowned upon by the Debian community to use the .deb format to
> publish these packages?
While it is fine to publish .deb packages outside of Debian, it is
usually better for everyone and recommended by Debian to get them
On Fri, 2022-01-21 at 10:06 +0100, Markus Blatt wrote:
> I assume that this version dependency was added when the packages
> were built some time ago.
Correct, see the dh_shlibdeps, dpkg-shlibdeps, deb-shlibs,
deb-symbols and dpkg-gensymbols manual pages for details.
> What is the recommend way
On Thu, 2022-01-13 at 20:54 +, John Scott wrote:
> You might like to have a look at this mail from Ben Hutchings:
> https://lists.debian.org/msgid-search/179d6d32466dd13962a3aab251c45242fbf2d8ae.ca...@decadent.org.uk
> The reason that none of the other Wi-Fi firmware packages have them is
>
On Sat, 2021-12-25 at 18:25 +, John Scott wrote:
> https://mentors.debian.net/debian/pool/main/c/carl9170fw/carl9170fw_1.9.9-399-gcd480b9-1.dsc
Some things that prevent the upload of this package:
I don't think udebs are needed for firmware packages, none of the other
WiFi firmware packages
Giulio Paci wrote:
> 3) what is the most appropriate solution.
As I understand it, floating point values should not be compared
without some kind of accuracy/precision factor. Zero idea about the
best reference for how to do it correctly, but here is a random one:
On Mon, 2021-11-22 at 08:47 +0200, Tommi Höynälänmaa wrote:
> Package theme-d-gnome was scheduled for autoremoval on 2021-11-21 but
> it looks like the package has not been removed yet.
It looks like the autoremoval was processed:
$ apt-cache madison theme-d-gnome
theme-d-gnome |0.9.6-3 |
On Sun, 2021-11-21 at 21:22 +0100, Marc Haber wrote:
> Is there a less ugly way?
Send upstream a patch to create a directory structure like this:
src/
examples/
c/
c++/
If you're only after workarounds, there are two options:
Run dh_installexamples twice. First install the C++
On Sat, 2021-10-30 at 20:47 +, Joshua Peisach wrote:
> I contacted upstream about tokenize-rt. It seemed perfect to put into
> upstream Python because it's small, and its tiny popularity but is
> used by many of his other apps which rely tokenize-rt. I approached
> him in a GitHub issue and
On Fri, 2021-10-29 at 15:28 +0200, Alec Leamas wrote:
> Other solutions could be creating a file like VERSION with relevant git
> data and add that to the distribution. That file can normally not be
> checked into git, it's a chicken and egg problem. The solution is to add
> the logic to
On Sun, 2021-10-24 at 14:24 +0200, wf...@niif.hu wrote:
> libraries (like libswtpm_libtpms.a)
This library sounds like an embedded code copy, if it is one, please
follow the advice on this wiki page. libtpms is already in Debian.
https://wiki.debian.org/EmbeddedCopies
--
bye,
pabs
On Tue, 2021-10-19 at 09:03 +0200, Ole Streicher wrote:
> At least some of them are not really suitable to be packaged as
> separate public packages. The two submodules in question (AOcommon,
> schaapcommon) are personal utility functions of the upstream authors
> which are not intended for
On Tue, 2021-10-12 at 14:43 +0200, Ole Streicher wrote:
> https://gitlab.com/aroffringa/wsclean
>
> He uses git submodules
These all look like embedded code copies, so I suggest packaging them
separately instead of including them the wsclean source tarball.
https://wiki.debian.org/EmbeddedCopy
On Wed, 2021-10-06 at 13:50 +0900, notebook wrote:
> When I asked for the package source back then, I was referred only to
> the debian tarball. I.e. I was not aware of anything else existing.
The package source and the upstream source are two different things.
When creating a fork of an
On Tue, Oct 5, 2021 at 7:06 AM notebook wrote:
> I'm working on the "Gjiten" package ([1]). It was kind of abandoned and used
> Gtk2.
> I upgraded it to Gtk3 and did some further development on it (see [2]).
>
> I'd like to get the new codebase into the debian repos. If I understand
>
On Sat, Sep 11, 2021 at 2:26 PM Marc Haber wrote:
> What would debian-mentors' recommendation be? Your hints will be
> appreciated.
To prevent installation of an static aide with a incompatible nss
libraries, you could get glibc to add Provides: libc-nss-abi (= N) or
Provides: libc-nss-abi-N and
On Wed, Aug 11, 2021 at 1:54 PM Peymaneh Nejad wrote:
> I am working on packaging the Caddy web server. Caddys github repo[1] only
> includes the platform-agnostic files (mostly .go source files) needed for
> building and testing.
> distro-specific files such as systemd unit files,
On Tue, Aug 10, 2021 at 11:24 AM Peymaneh Nejad wrote:
> I realised later that this package actually break the build, and that this
> can be solved by packaging _older_ version of the dependency package (that's
> also what upstream does.
The best option is to send upstream a patch to fix the
On Sat, Aug 7, 2021 at 10:54 PM Brian Thompson wrote:
> How should a new maintainer go about closing old bug reports?
I noticed that you have been:
Closing bug reports without any explanation.
Closing what looks like legitimate feature requests.
Neither of these is a good idea IMO.
--
bye,
On Sat, Aug 7, 2021 at 10:54 PM Brian Thompson wrote:
> What's the best way to go about handling old bug reports?
Triage them; go through each bug, try to find out if it was fixed and
which version it was fixed in. For the definitely fixed bugs, close
them with a versioned -done message. For the
On Thu, Jun 24, 2021 at 10:01 PM Hilmar Preuße wrote:
> uversionmangle=s/(\d)[_\.\-\+]?((RC|rc|pre|dev|beta|alpha)\d*)$/$1~$2/,\
...
> According to [1] the entry "uversionmangle=..." should handle the case
> that there could be beta/rc versions, which should be ignored. When
> doing an uscan now
On Thu, 2021-06-24 at 23:30 +0800, Tian Qiao wrote:
> I will suggest to upstream, remove these binary dependencies in
> subsequent code refactoring, and use some assembler libraries
> instead, such as Keystone. Thanks!
Switching to different dependencies shouldn't be necessary, just not
On Thu, 2021-06-24 at 00:46 +0800, Tian Qiao wrote:
> Besides, "nasm.exe" and "objdump.exe" are provided for the
> convenience of Windows users.
I suggest upstream should remove these from the source code and only
distribute them with their Windows binary packages. The build process
for the
On Wed, 2021-06-23 at 18:32 +0800, Tian Qiao wrote:
> On Jun 23, 2021, at 1:06 AM, Tobias Frost wrote:
>
> > shellcodes/data/linux/*bin
> > - Are they rebuilt during package build?
>
> these are similar to static resources, which help users quickly build
> shellcode when writing exploit
On Fri, Jun 18, 2021 at 8:30 AM Tobias Frost wrote:
> I suggest to read [1] and all linked documents, and recreate the package.
> You'll find dh_make(1) from the package dh-make useful to generate boiler
> plate
> templates for the debian directory. Those templates needs to be hand-edited
>
On Tue, Jun 8, 2021 at 6:54 AM clay stan wrote:
> Upstream support arm means the mobile arm chips, like Snapdragon, MediaTek,
> not arm PC, They are not supported by Debian.
Debian can run on ARM mobile chips, probably a non-mainline Linux
kernel from outside of Debian will be needed though.
On Wed, Jun 2, 2021 at 3:36 PM Tobias Frost wrote:
> Has this been discussed on e.g debian-legal or with the ftp masters
> beforehand?
FTR, Debian's patent policy is to only discuss them with lawyers,
never in public:
https://www.debian.org/legal/patent
On Tue, Jun 1, 2021 at 11:46 AM Steffen Möller wrote:
> I had a look and like the device. Conceptionally, it would be very
> interesting to learn if you can build the firmware for the Spartan-3
> also with Debian. It should be possible with Yosys. I do not mean that
> you need to Open Source
On Tue, Jun 1, 2021 at 10:39 AM Tobias Frost wrote:
> this seems to be a quite specific software for some quite specific evaluation
> board…
The chip seems like something useful for scientists and others dealing
with high speed analog signals. Looks like both the board and the
chips themselves
On Tue, May 25, 2021 at 1:53 AM John Scott wrote:
> Note that in their reference to building a 'Hello, world' program, the
> specification says that what makes the test superficial is that the
> library's functionality isn't used in the 'Hello, world' program, but
> merely linking against it is
On Fri, 2021-05-21 at 08:27 +0200, Tomaž Šolc wrote:
> Should I wait with this package until Bullseye is released?
Yes, or upload to experimental now and unstable after the release.
> If you think it makes more sense, I can simply drop it from the binary
> package.
I think it makes sense to
On Thu, 2021-05-20 at 20:28 +0200, Tomaž Šolc wrote:
> I contacted Tomaž Erjavec and Aleš Košir (one of the authors of
> aspell-sl). aspell-sl is currently unmaintained. The old website and the
> archive of releases were lost in a hard drive crash.
Some of it is available on archive.org, but
On Wed, May 19, 2021 at 8:51 AM Richard Hector wrote:
> Does that not depend on whether it does anything before dropping
> privileges? For example, a webserver can bind to low ports before
> dropping privilege. I imagine if the systemd service unit specified
> running as (eg) www-data, that
On Mon, May 17, 2021 at 12:51 PM Khoa Tran Minh wrote:
> I'm trying to write a new systemd unit for mini-httpd package, which is
> using lsb-base to init. Can I replace the old init script straight up, or
> do I have to maintain both the systemd unit and the old init script ?
Please make sure
On Thu, May 13, 2021 at 3:15 PM Tomaž Šolc wrote:
> The upstream homepage for this package is no longer available on the web. I
> continue to maintain this package since it is the only Slovenian spell checker
> available in Debian.
The Homepage is 404, but the site it was on still works. Have
On Wed, Apr 14, 2021 at 7:42 PM Pavel Machek wrote:
> I don't think forking ofono is good idea.
I'd like to point out that this isn't ofono that is being forked, but mmsd.
--
bye,
pabs
https://wiki.debian.org/PaulWise
On Fri, Apr 2, 2021 at 6:26 PM Tong Sun wrote:
> Is that possible with salsa.debian.org? thx
Preferences -> Notifications -> Receive notifications about your own activity.
--
bye,
pabs
https://wiki.debian.org/PaulWise
On Mon, Mar 29, 2021 at 8:03 PM Onsemeliot wrote:
> I suspect adapting the old Trigger Rally Debian package isn't as
> complicated as it seems to me right now.
It is made slightly more complicated by this being a team maintained
package that is stored in a git repository.
If it weren't stored
On Sun, Mar 7, 2021 at 5:07 AM Tong Sun wrote:
> Is it OK that I simply `rm` them, like `rm /etc/dnsmasq.d/dbab-*`?
I think so, yes.
--
bye,
pabs
https://wiki.debian.org/PaulWise
On Sun, Mar 7, 2021 at 4:45 AM Tong Sun wrote:
> Ah, indeed. the two files are modified after the package was
> installed. Actually they are generated, not from within the package.
Configuration files should either be conffiles installed in the .deb
or files created by the package at
On Sun, Mar 7, 2021 at 3:31 AM Tong Sun wrote:
> after I remove the package
Did you remove the package or purge it? Removing it will not run the
postrm, but purging it will.
> the last two files ... still remains and are left behind, while the first one
> was indeed gone.
Were the two files
On Sun, Feb 21, 2021 at 9:56 PM Tong Sun wrote:
> What's the correct way to install/enable/remove the daemon from my
> package inside the post install/rm scripts?
Usually debhelper will do the right thing without any configuration.
--
bye,
pabs
https://wiki.debian.org/PaulWise
On Sun, Feb 14, 2021 at 12:36 PM Kavan Mevada wrote:
> One manifest file to generate all required files for packaging so we don't
> have to look at multiple files
There was a project created similar to this last year, but the project
was abandoned in the end, you might want to contact the
On Tue, Feb 9, 2021 at 6:48 PM Ross Gammon wrote:
> I have an upload stuck in the upload queue due to an expired key, and I
> would like upload my newly unexpired key to the Debian keyservers so
> that it is eventually unblocked.
>
> But I get this error:
> $ gpg -v --keyserver keyring.debian.org
On Sun, Feb 7, 2021 at 5:34 AM Tong Sun wrote:
> The bug report is at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958899
>
> Basically I was trying to start/stop a Perl based http server.
> I do have one that almost like that,
> https://github.com/suntong/dbab/blob/master/bin/dbab
> but
On Sat, Feb 6, 2021 at 9:31 PM Tong Sun wrote:
> I have a dilemma,
I suggest deleting your existing init script and instead using the
example from the init-d-script(5) manual page.
> However, sourcing /lib/init/init-d-script will break in some cases,
> because of which, I had a bug opened
On Sat, Feb 6, 2021 at 9:02 PM Tong Sun wrote:
> Is there a way to make both systemd and sysvinit Debian happy, for my
> Perl based daemon?
sysvinit is not compatible with systemd units. You will need to add an
init script, see the simple example in the init-d-script(5) manual
page, unless your
On Sat, Feb 6, 2021 at 9:20 PM Tong Sun wrote:
> My package version is incorrect. It is currently "1.5.01-1", which I
> later learned that it should be "1.5.1-1" instead.
These two versions are considered equal by dpkg:
$ dpkg --compare-versions "1.5.01-1" eq "1.5.1-1" ; echo $?
0
$ dpkg
On Tue, 2021-02-02 at 07:19 -0300, Victor David Santos wrote:
> bundle.rb is still useful for the way I currently create an
> executable for Windows. deb.sh would still be useful to copy the
> files to the package structure (or is there a better way to do this?)
The intro guide I linked will
On Mon, 2021-02-01 at 08:36 -0300, Victor David Santos wrote:
> Thanks for the detailed feedback. Just to make sure, not all of these
> items you pointed out are mandatory for the package to be accepted,
> right?
All of the points I made are my personal opinions. There are a range of
different
On Sun, Jan 31, 2021 at 8:36 PM Victor David Santos wrote:
> I would like to distribute my open source platformer game in the official
> Debian repositories.
Please review our guide for new package maintainers:
https://mentors.debian.net/intro-maintainers
Some things you might want to think
1 - 100 of 2536 matches
Mail list logo
