On Sat, Jun 05, 2021 at 07:43:54AM +1000, Jon Gough wrote:
>
> On 9/5/21 5:40 pm, Andrey Rahmatullin wrote:
> > On Sun, May 09, 2021 at 04:41:13PM +1000, Jon Gough wrote:
> > > My conclusion is that application plugin mangers should make use of the
> > > pla
On Tue, May 25, 2021 at 04:23:21PM -0400, Polyna-Maude Racicot-Summerside wrote:
> When someone write a message saying they are looking for a sponsor, does
> are person who already maintain the package but would like someone to
> support them in the uploading of the package ?
Not sure what do you m
On Tue, May 25, 2021 at 02:46:06PM -0400, Polyna-Maude Racicot-Summerside wrote:
> Hi !
> I've seen many message on the debian bugs list saying that a specific
> package is orphaned and looking for a maintainer.
>
> What would be the best way to adopt a package ?
Record that in the WNPP bug as htt
On Thu, May 20, 2021 at 07:32:53AM +0200, Jan Gru wrote:
> Those are de-facto runtime dependencies, but ~pcodedmp~ is required by
> ~oletools~ to run the `python setup.py tests` during the build of oletools,
> so it is kind of a build dependency, too. I assume disabling those tests
> selectively, w
On Tue, May 18, 2021 at 05:34:02AM -0400, Albretch Mueller wrote:
> On 5/18/21, Andrei POPESCU wrote:
> > https://tracker.debian.org/pkg/bitz-server
>
> On 5/18/21, Jörg Frings-Fürst wrote:
> > Hello Albretch,
> > bitz-server has 4 RC-Bugs[1], which could not be fixed by me.
> > No fixes came fr
On Sun, May 09, 2021 at 04:33:54PM +0200, josef.stry...@email.cz wrote:
> I would like to become a sponsored maintainer of the Papirus-folders package
> (allows to change the color of folders), but I don't know which team to ask
> for sponsoring.
Please follow https://mentors.debian.net/intro-maint
On Sun, May 09, 2021 at 10:07:38AM +0300, Martin Atukunda wrote:
> > > where else could the 'system' files be placed?
> >
> > Not sure what you mean about system files.
> > My interpretation would be that "system" files come from the .deb. Here,
> > Debian policy is the reference, and §9 refers to
On Sun, May 09, 2021 at 04:41:13PM +1000, Jon Gough wrote:
> My conclusion is that application plugin mangers should make use of the
> platform installation process for installing and uninstalling plugins as it
"the platform installation process" sounds like using debs, am I wrong?
> would appear
On Tue, May 04, 2021 at 04:46:42AM +0200, Alec Leamas wrote:
> Touching files under $HOME in a postrm script is obviously a bad idea.
> However, a colluegue insists in trying to make me do this.
Under which of the home dirs? Normally it just doesn't make sense to find
all real users and then find a
On Fri, Apr 23, 2021 at 01:18:27PM +0200, Harald Dunkel wrote:
> I have a new version of mg ready to go, but I am concerned that
> pushing it to Salsa might trigger an unwanted change to Bullseye
> during code freeze. Does it?
Pushes to salsa don't change anything in the actual archive. But you may
On Mon, Apr 12, 2021 at 10:42:47PM +0200, Hilmar Preuße wrote:
> I have a dumb question regarding lintian tag "E: embedded-library". For the
> package texworks the lintian tag is reported, even for an build from the
> actual vcs.
>
> Unfortunately I have no clue how this lintian error is created.
On Fri, Mar 26, 2021 at 12:23:57PM +0100, Peymaneh Nejad wrote:
>
> Hello,
>
> someting awkward happened to me: I just filed a bug via mail at wnpp, but I
> accidentily left out the ITP tag in the subject line
> (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985931)
>
> I searched through th
On Tue, Mar 16, 2021 at 06:13:43PM -0400, Aaron Boxer wrote:
> > > Hello,
> > > I have what I hope is a fix for the build failure on i386.
> > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985116
> > >
> > > Version 7.6.6-3 is uploaded to the mentors site,
> > > and should be available shortl
On Tue, Mar 16, 2021 at 01:05:11PM -0400, Aaron Boxer wrote:
> Hello,
> I have what I hope is a fix for the build failure on i386.
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985116
>
> Version 7.6.6-3 is uploaded to the mentors site,
> and should be available shortly. Could someone pleas
On Tue, Mar 16, 2021 at 01:05:11PM -0400, Aaron Boxer wrote:
> Hello,
> I have what I hope is a fix for the build failure on i386.
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985116
>
> Version 7.6.6-3 is uploaded to the mentors site,
> and should be available shortly.
It's still not.
On Sun, Mar 07, 2021 at 01:50:07PM -0500, Tong Sun wrote:
> I found that origtargz unable to detect upstream new release for me.
From origtargz(1):
"The version number for the tarball to be downloaded is determined from
debian/changelog."
--
WBR, wRAR
signature.asc
Description: PGP signature
On Fri, Feb 12, 2021 at 11:21:38AM +0100, Hilmar Preuße wrote:
> > > You can't adjust anything to get more than 4GB virtual memory on 32-bit
> > > architectures.
> > > You can try adjusting compilation/linking parameters to make the
> > > compiler/linker use less memory though (not sure if the sugg
On Fri, Feb 12, 2021 at 10:17:06AM +0100, Andreas Tille wrote:
> in the build log[1] I found
>
>virtual memory exhausted: Operation not permitted
>
> I wonder whether this could be simply solved by adjusting the hardware /
> emulation parameters of the according autobuilder.
>
> Am I missing
On Sun, Feb 07, 2021 at 11:53:16PM +0100, Kai-Martin Knaak wrote:
> just told me that all the packages were already there. It concluded
> "Nothing to upload".
It just checks the presence of an .upload file. You can remove it or pass
-f.
--
WBR, wRAR
signature.asc
Description: PGP signature
On Mon, Jan 18, 2021 at 03:15:12PM +0100, Patrick Vavrina wrote:
> My name is Patrick Vavrina. I live in Geneva, Switzerland. I am a GNU/Linux
> System Engineer and a Web Administrator.
>
> I would like to contribute to Debian as a maintainer.
Then please go ahead, prepare package uploads and a
On Sat, Jan 09, 2021 at 11:27:36AM -0500, Tong Sun wrote:
> Hi,
>
> Is there anything else I need to do after uploading my upgraded
> package to ftp-master?
>
> My following upgraded package has been uploaded to ftp-master a while ago,
>
> Checking signature on .dsc: ../ffcvt_1.6.0-1.dsc: Valid
On Wed, Dec 23, 2020 at 09:44:18AM -0500, Aaron Boxer wrote:
> Dear Mentors.
> I submitted the libgrokj2k package over 6 months ago, and I am not clear on
> its current status.
> It has been accepted into the NEW repo, and has been released to UNSTABLE.
> Are there any other steps needed before it
On Fri, Dec 18, 2020 at 04:07:50PM +0100, Andreas Tille wrote:
> On Fri, Dec 18, 2020 at 07:37:12PM +0500, Andrey Rahmatullin wrote:
> > On Fri, Dec 18, 2020 at 03:32:01PM +0100, Andreas Tille wrote:
> > > I tried no override_dh_shlibdeps in shasta debian/rules, which
On Fri, Dec 18, 2020 at 03:32:01PM +0100, Andreas Tille wrote:
> Hi,
>
> I tried no override_dh_shlibdeps in shasta debian/rules, which has lead
> to:
>
> dpkg-shlibdeps: error: cannot find library
> /usr/lib/python3/dist-packages/shasta.cpython-39-x86_64-linux-gnu.so needed
> by debian/shasta/
On Sun, Dec 06, 2020 at 07:32:13PM +0100, Jose G. López wrote:
> D: dh_python3 fs:260: package scid details = {'requires.txt': set(),
> 'egg-info': set(), 'nsp.txt': set(), 'shebangs': {/usr/bin/python2},
> 'public_vers': set(), 'private_dirs': {}, 'compile': False, 'ext_vers':
> set(), 'ext_no_
On Fri, Dec 04, 2020 at 10:08:29PM +0100, Benoît Rouits wrote:
> Thank you for your reply.
>
> I used to put this line:
> Build-Depends: debhelper-compat (= 12), ...
>
> Should I then remove "-compat" like this ?
> Build-Depends: debhelper (= 13), ...
No. Build-Depends: debhelper is a normal buil
On Fri, Dec 04, 2020 at 08:39:26PM +0100, Benoît Rouits wrote:
> I use debhelper but I don't use specific features
> of debhelper 13.
> Anyway, should I set debhelper = 13 as build dependency
Yes.
> or can I set debhelper >= 12 to be more flexible
> for transition from sid to testing and to stable
As I've already told you yesterday on IRC, the test succeeds with -O2,
which is set when building the package.
--
WBR, wRAR
signature.asc
Description: PGP signature
On Tue, Dec 01, 2020 at 09:08:23PM +0100, Andreas Tille wrote:
> Control: tags -1 pending
>
> Hi,
>
> upstream of fis-gtm package[1] confirmed that the build needs some root
> permissions. Thus I've set
>
>Rules-Requires-Root: yes
There is no "Rules-Requires-Root: yes", see the Policy.
--
On Tue, Nov 17, 2020 at 02:53:10PM +0100, Mechtilde Stehmann wrote:
> version=4
> opts=\
> filenamemangle=s/.*=(.*)/$1/ \
> https://pdfbox.apache.org/download.cgi
> .*/jbig2-imageio-(\d(\.\d)*)-src\.zip&action=download
To fix the version extraction, replace (\.\d)* with (?:\.\d)* to make it
non
On Mon, Nov 16, 2020 at 02:04:30PM +, 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.
>
>
On Mon, Nov 16, 2020 at 01:13:01AM +1100, Stuart Prescott wrote:
> Hi Daniele
>
> I've not looked carefully at this package at all, but this one stood out:
>
> >librobottestingframework-python2 - Robot Testing Framework -
> > RTF_python library
>
> Now is not the time to be introducing thin
On Sun, Nov 15, 2020 at 03:03:08PM +0100, Fabien Givors (Debian) wrote:
> However, I found out that there were a sudden (yet relative) rise in popcon
> usage: https://qa.debian.org/popcon.php?package=obsession so, there are
> users…
That's because openbox now Recommends it.
--
WBR, wRAR
signatu
On Tue, Nov 10, 2020 at 05:17:26PM +0200, Juhani Numminen wrote:
> Hi,
>
> Maarten L. Hekkelman as the package maintainer asked for my help with bug
> #973526
> but I have to forward his request to debian-mentors.
>
> The package libzeep failed to build on amd64, apparently because of a SIGABRT
On Thu, Nov 05, 2020 at 10:58:16AM -0500, Tong Sun wrote:
> So I just ignore it, without trying to fix blhc?
It's not a blhc problem, nothing to fix there.
It cannot know which of the compilation commands in your build process are
important.
--
WBR, wRAR
signature.asc
Description: PGP signature
On Thu, Nov 05, 2020 at 01:32:49PM -0300, Carlos Henrique Lima Melara wrote:
> I think you can ignore for now but would be really nice if you could report
> it to the upstream or fill a bug in the blhc package.
It's not a bug in blhc.
--
WBR, wRAR
signature.asc
Description: PGP signature
On Thu, Nov 05, 2020 at 08:49:33AM -0500, Tong Sun wrote:
> removing it yields
> https://salsa.debian.org/debian/shc/-/jobs/1138279
> the same as where it all begins --
> https://salsa.debian.org/debian/shc/-/jobs/1126858
So it even shows the commands that it thinks are incorrect, and you can
see t
On Thu, Nov 05, 2020 at 08:08:17AM -0500, Tong Sun wrote:
> > > I used
> > >
> > > export DEB_BUILD_MAINT_OPTIONS = hardening=+all
> > >
> > > to fix the hardening issue, but it yields the following error from blhc:
> > >
> > > CPPFLAGS missing (-D_FORTIFY_SOURCE=2)
> > >
> > > See https://salsa.de
On Wed, Nov 04, 2020 at 10:28:04PM -0500, Tong Sun wrote:
> Hi,
>
> I used
>
> export DEB_BUILD_MAINT_OPTIONS = hardening=+all
>
> to fix the hardening issue, but it yields the following error from blhc:
>
> CPPFLAGS missing (-D_FORTIFY_SOURCE=2)
>
> See https://salsa.debian.org/debian/shc/-/j
On Wed, Oct 28, 2020 at 03:23:41PM -0400, Tong Sun wrote:
> > (it installed the -dev package from sid because you didn't add a version
> > constraint to require the version from experimental)
>
> Ok, to add a version constraint, is it OK that I use the following to
> replace all libgit2 dependents
On Tue, Oct 27, 2020 at 11:21:57PM -0400, Tong Sun wrote:
> So I build with experimental build-dep via:
>
> sbuild -s -v -A --no-clean-source -d unstable --extra-repository='deb
> http://deb.debian.org/debian experimental main'
> --build-dep-resolver=aspcud gnuastro
(it installed the -dev package
On Tue, Oct 27, 2020 at 04:38:35PM -0400, Nick Black wrote:
> I maintain the notcurses package, which is already in the
> archive. Recently, the soname changed, necessitating a new
> package name (libnotcurses1 -> libnotcurses2). I understand this
> needs go through NEW, but alas, I've been unable
On Fri, Oct 23, 2020 at 01:19:04PM -0400, Tong Sun wrote:
> I'm currently helping with the library transition for libgit2-dev.
Then I would expect you to ask the maintainers for coordination and/or
help.
> This is the first time I'm doing the library transition so I'm
> following the library trans
On Fri, Oct 23, 2020 at 12:25:19PM -0400, Tong Sun wrote:
> > > > > PS, here are all libgit2 related packages installed in my system, and
> > > > > their versions:
> > > > >
> > > > > libgit2-1.0:amd64_1.0.0+dfsg.1-1
> > > > > libgit2-28:amd64_0.28.5+dfsg.1-1
> > > > > libgit2-build-deps_1.0.0+dfsg
On Fri, Oct 23, 2020 at 11:58:03AM -0400, Tong Sun wrote:
> On Fri, Oct 23, 2020 at 11:50 AM Andrey Rahmatullin wrote:
> >
> > On Sat, Oct 17, 2020 at 03:27:40PM -0400, Tong Sun wrote:
> > [skipped as already answered in private]
>
> Strange, I didn't get any
On Sat, Oct 17, 2020 at 03:27:40PM -0400, Tong Sun wrote:
[skipped as already answered in private]
> One reason I can think of is that, my latest libgit2 is called
> libgit2-1.0 while the *old* one is called libgit2-28, which is in fact
> libgit2 v0.28.5+dfsg.1-1. Which one would debuild pick?
deb
On Mon, Oct 12, 2020 at 11:36:36AM +0200, Andreas Tille wrote:
> Control: tags -1 help
>
> Hi,
>
> while I've fixed the issue for arm64 the new version of bowtie seems to
> have some new assembly code where mips64el, ppc64el and others are
> stumbling upon [1]:
The reason it works on arm64 is
i
On Wed, Oct 07, 2020 at 03:44:57PM -0400, Tong Sun wrote:
> > Nice:
> > https://metadata.ftp-master.debian.org/changelogs//main/m/microsocks/microsocks_1.0.1-1_changelog
> >
> > Not sure why it's still here... maybe because it went to experimental only?
I don't think this should matter for the ment
On Tue, Sep 29, 2020 at 09:41:58AM -0400, Tong Sun wrote:
> On Tue, Sep 29, 2020 at 9:19 AM Andrey Rahmatullin wrote:
> >
> > On Tue, Sep 29, 2020 at 09:15:41AM -0400, Tong Sun wrote:
> > > > > Also, one dependent of libgit2-dev is librust-libgit2
On Tue, Sep 29, 2020 at 09:15:41AM -0400, Tong Sun wrote:
> > > Also, one dependent of libgit2-dev is librust-libgit2-sys-dev. and I see
> > >
> > > $ grep -B10 libgit2-dev debian/control
> > > Build-Depends: debhelper (>= 11),
> > > dh-cargo (>= 18),
> > > cargo:native ,
> > > rustc:native ,
>
On Tue, Sep 29, 2020 at 08:30:33AM -0400, Tong Sun wrote:
> So `libgit2-dev` only shows up once in calligra's debian/control file.
You need to check actual dependencies of binary packages (e.g. by looking at
debs with dpkg-deb -f), not your debian/control.
And libgit2-dev is a development package,
On Mon, Sep 28, 2020 at 09:55:17PM -0400, Tong Sun wrote:
> Of all the above 46 newly built binary-only packages, how can I tell
> which .so from them will link to libgit2-dev, and whether the
> libgit2-dev version linked is truly v1.0.0? Note this is more a
> generic question and not specific for
On Tue, Aug 25, 2020 at 10:39:50AM +0300, Andrius Merkys wrote:
> Buildd status page for libdatetime-perl [1] says that on kfreebsd-* its
> build dependencies are uninstallable, citing the following dependency
> tree (for kfreebsd-amd64, for example):
>
> libdatetime-perl build-depends on:
> - lib
On Sat, Aug 22, 2020 at 01:56:00PM +0200, Hilmar Preuße wrote:
> >> The person who did the upload for debian/0.7+git73896501cf-1 did not
> >> update the "upstream" branch, hence the tag was not created.
Actually, the person who did the "Upgrade to latest commit from github."
(92ff447) commit in 201
On Sat, Aug 22, 2020 at 01:08:52AM +0200, Hilmar Preuße wrote:
> gbp:error: Error running git push: To
> salsa.debian.org:debian-proftpd-team/proftpd-mod-case.git
> ! [rejected]d8074c6b03512b4001b8e1ea06737afd989f139a -> master
> (non-fast-forward)
>
> I did the "git pull", which says "Al
On Thu, Aug 20, 2020 at 02:15:07AM +, Paul Wise 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_Cor
On Thu, Aug 20, 2020 at 12:09:08AM +0200, gregor herrmann wrote:
> > > > > Are these acceptable caveats for a source package in contrib,
> > > > No, the package still needs to be built without network, using only its
> > > > contents and packages from Debian.
> > > > You also need to produce a pack
On Wed, Aug 19, 2020 at 02:31:10PM +, Alistair J R Young wrote:
> > > Are these acceptable caveats for a source package in contrib,
> > No, the package still needs to be built without network, using only its
> > contents and packages from Debian.
> > You also need to produce a package that can
Note that you replied to my email in private and I can't reply back as
your server blacklisted my IP.
--
WBR, wRAR
signature.asc
Description: PGP signature
On Wed, Aug 19, 2020 at 10:31:43AM +, Alistair J R Young wrote:
> I'm currently working on packaging a .NET Core utility for contrib (ITP here:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968331; current version of
> the package here: https://mentors.debian.net/package/systemd-genie/
On Thu, Aug 13, 2020 at 12:47:16PM -0700, A. Lewenberg wrote:
> I am trying to suppress some lintian errors in my package build. I see this
> error when running lintian:
> --
> E: stanford-spdb source: source-is-missing
> usr/share/spdb/vendor/assets/javascripts/bootstrap-4.4.1.min.js
> --
This is
On Sun, Aug 09, 2020 at 11:11:44PM +0200, Christian T. Steigies wrote:
> Hi,
> I am trying to upgrade a package, it seems I need to switch to a newer
> debhelper version with it, 9 seems to be too old. I did the upgrade by
> changing Build-Depends from debhelper (>= 9) to debhelper-compat (13) or 1
On Sun, Jul 26, 2020 at 02:50:31PM +0200, dettus wrote:
> So, my latest and greatest release comes with a "make check" target.
>
> The thing is, under Debian it requires an extra parameter.
>
> make SHA256_CMD=sha256sum check
>
> would be the correct one. My question is... How do I put this into
On Thu, Jul 16, 2020 at 07:23:18PM -0400, Scott Talbert wrote:
> Hi,
>
> Can anyone direct me to some examples of packages that use dh and generate
> various Debian packaging files? For example, a debian/control.in file
> that's processed to create debian/control during build.
>
> I've found exa
On Thu, Jul 16, 2020 at 08:42:00PM +0200, Nico Schlömer wrote:
> Thanks Andrey for looking into this. How did you find out it comes
> from hhdate's CMakeLists.txt?
1. I googled ONLY_C_LOCALE and found the project that uses it, the one
that includes that date.h, https://github.com/HowardHinnant/date
On Thu, Jul 16, 2020 at 08:04:20PM +0200, Nico Schlömer wrote:
> Hi everyone,
>
> I'm trying to build a package for waybar [1], and I'm running some
> test builds on a PPA. I'm inching close, but now there's something I
> cannot figure out: The build process adds the flag
> ```
> -DONLY_C_LOCALE=
On Sun, Jul 05, 2020 at 10:50:28AM +0100, Joan Moreau wrote:
> I have now managed to have debmake and debuild to run without errors
>
> I am running it on https://grosjo.net/tomboy-reborn-1.0.0.tar.gz
>
> The "debuild" command does create a ".deb" file. However the deb file
> is not instalable (
On Sat, Jul 04, 2020 at 09:35:15PM +0100, Joan Moreau wrote:
> When you say "write a proper source package ", are you referring to the
> actual ".deb" package ? or something else ?
I'm referring to a Debian source package. I've already linked you to
https://wiki.debian.org/Packaging/SourcePackage.
On Sat, Jul 04, 2020 at 08:39:36PM +0100, Joan Moreau wrote:
> (1) As a "software provider", what files are expected (besides the
> sources, the Makefile and the binary) ? ( please kindly refer to :
> https://github.com/grosjo/tomboy-reborn )
The sources and the build system to build them. Binaries
On Sat, Jul 04, 2020 at 06:06:05PM +0100, Joan Moreau wrote:
> Input file sare visibles on
> https://github.com/grosjo/tomboy-reborn/tree/master/packages
You are supposed to include thesoftware source in the package, not this.
So debian/ should be in the root of the repo.
> This is the exact ouptu
On Sat, Jul 04, 2020 at 05:57:51PM +0100, Joan Moreau wrote:
> Is there a web page stating the steps to go through, without all this
> complexity ?
>
> similar to the Arch :
> https://wiki.archlinux.org/index.php/AUR_submission_guidelines
https://mentors.debian.net/intro-maintainers is similar t
On Sat, Jul 04, 2020 at 05:38:05PM +0100, Joan Moreau wrote:
> Let's imagine I found it (using lazbuild most probably), then where
> should I put that command ?
override_dh_auto_build, assuming you use dh(1)
> How to specifiy the options needed ?
As usual in the command arguments.
> where to put
On Sat, Jul 04, 2020 at 04:57:37PM +0100, Joan Moreau wrote:
> Hi Boyuan,
>
> Thank you so much for your feedback.
>
> The program is to be compiled with Lazarus
> (https://packages.debian.org/buster/lazarus-ide ), this is pretty
> straighforward for anyone willing to compile from source.
>
> SH
On Wed, Jul 01, 2020 at 05:35:21PM +0100, Joan Moreau wrote:
> This is not a "source package" as the source is in Pascal (using Lazarus
> compiler package). Should I include the Pascal source also ?
You need to create a Debian source package that can be built to produce a
Debian binary package.
It
On Sat, Jun 27, 2020 at 02:45:53PM +0200, Martin wrote:
> Hi there!
>
> Hopefully this is the correct list.
>
> I want to submit some patches to packages: Can you please
> tell me what the appropriate/standard way is to do that?
Attach them to a bug report.
> P.S: The link "mentors.debian.net" o
On Thu, Jun 11, 2020 at 02:53:47AM -0400, Qianqian Fang wrote:
>
> when dh builds the library, the linking command of the libzmat.so file did
> include the -lz flag (and the linking was successful)
>
> gcc -shared -Wl,-soname,libzmat.so.1 -lz -o ../lib/libzmat.so zmatlib.o
With --as-needed e
On Tue, May 12, 2020 at 06:17:34PM -0400, Raymond Li wrote:
> Hi,
>
> I maintain a popular lockscreen called i3lock-color. I've filed an ITP for
> it and have a .deb package ready. I need a .changes file to use dput to
> upload it to the mentors thinggy, but I have no idea how to get that file
> o
On Mon, Apr 27, 2020 at 12:19:36AM +0200, Ben Tris wrote:
> Now I found wordpress and the maintainer says he needs a binary upload.
> The given reason: the theme is new
> As I understand, that is not allowed in any case.
> What advice can I give, or what should have been done?
>
> https://tracker.
On Sat, Apr 25, 2020 at 02:53:51PM -0400, Aaron Boxer wrote:
> Hello,
> My library can use SIMD vector operations such as AVX2 if available on
> system.
> What is the best way of managing this ?
Runtime detection.
> Also, I tried logging onto #debian-mentors on freenode, but I got a message
> ab
On Fri, Apr 24, 2020 at 07:29:40AM -0700, Matthew Fernandez wrote:
> The arm64 failure [2] looks legitimate (though I
> don’t understand why excuses also says “arch:arm64 not built yet”),
It says it cannot run autopkgtests for arm64 because the binary isn't
built yet.
> the mipsel failure [3] look
On Sat, Apr 18, 2020 at 03:03:55PM +0200, Marcelo Zimbres wrote:
> I would like to find someone to sponsor my package tsvtree to include
> it in debian. The package is already packaged in .deb format and an
> ITP Bug has been filled.
>
> Please, let me know if you are interested.
>
> Package: htt
On Fri, Apr 10, 2020 at 12:55:32PM -0400, Aaron Boxer wrote:
> Hello!
>
> Is there a delay between when I upload a new package and when it shows
> up on the web site? I just uploaded a new package but I don't see it in "My
> Packages".
Yes. Wait for the confirmation email (assuming you did everyth
On Thu, Apr 09, 2020 at 11:13:26AM -0400, Roberto De Oliveira wrote:
> I decided to create a NMU for materia-gtk-theme based on comments of
> this thread[1], I sent by email a patch[2] created with nmudiff help,
> the tags related to this bug (945847) changed to "patch, pending"
Yes, your email cha
On Sun, Apr 05, 2020 at 12:16:16PM +0200, Fabrice BAUZAC-STEHLY wrote:
> Andrey Rahmatullin writes:
>
> > On Sat, Apr 04, 2020 at 11:36:03PM +0200, Fabrice BAUZAC-STEHLY wrote:
> >> - By building the upstream source (main)? By packaging the upstream
> >> bina
On Sat, Apr 04, 2020 at 11:36:03PM +0200, Fabrice BAUZAC-STEHLY wrote:
> - By building the upstream source (main)? By packaging the upstream
> binary (contrib)?
Pre-built binaries are for non-free, not for contrib. Contrib is strictly
DFSG-free.
--
WBR, wRAR
signature.asc
Description: PGP si
On Sat, Apr 04, 2020 at 06:53:55PM +0530, Nilesh Patra wrote:
> >From the logs, in the last message[2] it looks like an import-error for
> '_libsbml' file which corresponds to libsbml (with python3-sbml5 as a
> provide) package. When I dug into looking at libsbml, I noticed that the
> relevant file
On Sat, Apr 04, 2020 at 02:46:26PM +0200, Juergen Neumann wrote:
> Hi all!
>
> I would like to file an ITP for DMX - The Context Machine [1], formerly
> known as DeepaMehta [2]. As this will be my first project for Debian I
> am kindly looking for a sponsor. So far I barely managed to create a
> f
On Fri, Mar 27, 2020 at 07:24:38AM -0700, Matthew Fernandez wrote:
> Hi Andreas,
>
> I can’t reproduce this either, but in case your subject was hinting at a
> suspected cause, I don’t think this is it. The output shows CMake
> successfully finding Pthreads.
But the build fails with "/usr/bin/ld.g
On Thu, Mar 26, 2020 at 11:51:59AM -0400, Calum McConnell wrote:
> Okay, thanks: but isn't my new package a non-native package?
Is it your package or just a rebuild of an existing 3rd-party native one?
> Yes, the upstream happens to be a Debian redistribution: but there is an
> "upstream source" a
On Wed, Mar 18, 2020 at 01:49:29PM -0400, Calum McConnell wrote:
> calum@CalumsDebianSupreme:~/package/boot-repair/boot-repair_4ppa69-1$ ls
> boot-repair_4ppa69.orig.tar.gz debian docs etc po usr
The orig tarball must be in the parent directory.
> calum@CalumsDebianSupreme:~/package/boot-repa
On Tue, Mar 17, 2020 at 02:36:15PM +0100, Timo Röhling wrote:
> I've recently looked into upgrading the Qhull library for the Debian
> Science Team. The upstream SOVERSION remained unchanged (7), but
> abi-compliance-checker says that the ABI is incompatible, and quite
> seriously so. Clearly, I ca
On Mon, Mar 16, 2020 at 11:56:07PM +0100, Adam Borowski wrote:
> > > $ dput mentors fonts-jetbrains-mono_1.0.3-1_amd64.changes
> > > Package has already been uploaded to mentors on mentors.debian.net
> > > Nothing more to do for fonts-jetbrains-mono_1.0.3-1_amd64.changes
> >
> > And… basically rep
On Tue, Mar 10, 2020 at 05:57:15PM +0100, Sepi Gair wrote:
> Hello,
>
> I've got a sponsor for my package, the package now is pending for
> upload.
What do you mean?
--
WBR, wRAR
signature.asc
Description: PGP signature
On Mon, Mar 09, 2020 at 09:35:17PM +0100, rosea.grammostola wrote:
> > > If you just want to package non-session-manager, why not:
> > > 1. Download the tarball from here:
> > > https://git.tuxfamily.org/non/non.git/tag/?id=non-session-manager-v1.2.0
> > > (or the github mirror - whichever is best)
On Mon, Mar 09, 2020 at 11:02:03PM +0100, rosea.grammostola wrote:
> > how did you
> > resolve the NTK-fork dep and the waf evil?
>
> About he Waf evil, upstream developer told me this:
>
> "There was an issue a while I ago that I fixed related to how unique the
> shipped WAF binary is. I think i
On Mon, Mar 09, 2020 at 03:11:04PM -0600, Nicholas D Steeves wrote:
> src:non (or src:non-daw) would generate
> bin:non-{timeline,sequencer,mixer,session-manager}. Andrey, is the
> simplest method still debian/bin-pkg-name0.install and
> debian/bin-pkg-name1.install + simple glob patterns, and/or
On Mon, Mar 09, 2020 at 08:58:26PM +0100, Ross Gammon wrote:
> If you just want to package non-session-manager, why not:
> 1. Download the tarball from here:
> https://git.tuxfamily.org/non/non.git/tag/?id=non-session-manager-v1.2.0
> (or the github mirror - whichever is best)
That's just a snapsho
On Mon, Mar 09, 2020 at 03:20:26PM +0100, rosea.grammostola wrote:
> > You just need to create a source tarball that is able to build the project
> > you need. For that you'll need to find out which common files are also
> > needed.
> > You'll need to do it manually each time you need to upload a n
On Mon, Mar 09, 2020 at 02:26:49PM +0100, rosea.grammostola wrote:
>
> On 3/9/20 2:11 PM, Andrey Rahmatullin wrote:
> > > You can build each project independently.
> > It doesn't matter.
> > If you are able to split this repo into separate source packages, do it,
On Mon, Mar 09, 2020 at 01:07:34PM +0100, rosea.grammostola wrote:
> > > This git repo contains four packages, but I only want to package one. How
> > > to
> > > deal with this situation via git-buildpackage? (Upstream sources kept in
> > > the
> > > upstream branch and the the debian in the mast
101 - 200 of 1104 matches
Mail list logo
