On Mon, Sep 04, 2023 at 12:28:01PM +0200, Preuße, Hilmar wrote:
> Hi all,
>
> I'm trying to upload a new package for dvisvgm[1]. Unfortunately this does
> not work: the dput command runs fine, but I did not even got the E-Mail that
> the upload was successful and the package is processed.
> In
On Mon, Sep 04, 2023 at 10:33:12AM -0400, Tong Sun wrote:
> With current cloud-compiling approaches, how should we make sure that
> the built package works for the older x86_64 CPUs possible, and especially
> about this Q16 compilation for ImageMagick?
>
> PS, the compilation is done via
On Thu, Nov 02, 2023 at 07:54:16AM +0200, Tommi Höynälänmaa wrote:
> WWW page https://wiki.debian.org/binNMU doesn't mention the case arch:all
> package depending another arch:all package when it discussed making packages
> binNMU safe. How is this case handled?
arch: all packages arent rebuilt so
This ships a file named /usr/bin/art. I'm not sure if it's a good idea by
itself, but also the artemis package also ships a file with this name
(which I'm also not sure is a good idea) and so you should follow the
first paragraph of
https://www.debian.org/doc/debian-policy/ch-files.html#binaries
On Mon, Oct 30, 2023 at 06:18:42PM +0100, Santiago Vila wrote:
> > W: See /var/cache/pbuilder/base.cow/debootstrap/debootstrap.log for details
> > (possibly the package /var/cache/apt/archives/usr-is-merged_38_all.deb is
> > at fault)
>
> Try
> DEBOOTSTRAPOPTS="--merged-usr"
>
> in your
On Tue, Oct 10, 2023 at 09:07:16PM +0100, Oyindamola Olatunji wrote:
> Hello everyone,
>
> I am trying to update the mmlib package to upstream 1.4.2, however, I keep
> getting this salsa build error log with sphinx.
>
> https://salsa.debian.org/med-team/mmlib/-/jobs/4787422#1219
>
> The sphinx
On Fri, Dec 23, 2022 at 09:18:48PM +, Peymaneh wrote:
> Dear mentors list,
>
> a package that I maintain[1] creates a new system-user and -group ("caddy")
> and creates a homedirectory in /var/lib/caddy upon installation[2] intended
> for the systemd service file.
>
> When purging the
On Thu, Dec 29, 2022 at 11:37:00AM -0600, Ryan Pavlik wrote:
> For completeness, in addition to pbuilder/cowbuilder and sbuild, there is
> also whalebuilder which uses Docker.
If going for completeness,
https://wiki.debian.org/SystemBuildTools#Package_build_tools lists more
than these three
On Sun, Jan 29, 2023 at 03:45:26PM +0100, Lorenzo wrote:
> > > One problem with the tar.gz is that debian/gbp.conf has
> > > compression = xz
> > So this configuration is wrong ad you need to change it.
> I didn't write in my previous message, but the watch file of this
> project looks for a
On Mon, Jan 30, 2023 at 12:53:24PM +0100, Lorenzo wrote:
> > > > > One problem with the tar.gz is that debian/gbp.conf has
> > > > > compression = xz
> > > > So this configuration is wrong ad you need to change it.
> > > I didn't write in my previous message, but the watch file of this
> > >
On Mon, Jan 30, 2023 at 08:30:26PM +0100, Lorenzo wrote:
> > But overall you need to make sure the SVN repo contains the
> > same files as the published tarball, otherwise the compression
> > difference is not the largest problem you could have.
> right, I should have excluded the .svn directory
On Fri, Jan 27, 2023 at 06:02:34PM +0100, Lorenzo wrote:
> Hello mentors,
>
> I want to import a new svn snapshot to update a Debian package,
> the salsa git repo is already configured for gbp, so I did
>
> $ gbp import-orig -u1.5+svn38408 ../upstreamsvn/mplayer
>
> upstream/mplayer is a
On Fri, Jan 27, 2023 at 07:49:21PM +0100, Mechtilde Stehmann wrote:
> Hello Lorenzo,
>
> please use a special gbp.conf.
It would be much more useful if you provided the actual option for this.
(as far as I know it doesn't exist)
Unless you mean something else by "special".
> More information you
On Wed, Mar 22, 2023 at 01:48:39PM +0100, Robin Alexander wrote:
> Hi,
>
> I am in charge of creating debian packages for the Opendigitalradio mmbtools
> (https://www.opendigitalradio.org/mmbtools) and as such, I:
> - am proposing/pushing debian packages to unstable
> - manage the
On Wed, Mar 22, 2023 at 02:42:28PM +0100, Robin Alexander wrote:
> Hi Mechtilde and Andrey,
>
> Got it for the official debian repository. In a nutshell:
> - Push to mentors once the freeze is released (ie, after bookworm is
> released)
> - Once package in unstable/testing, push a backport to
On Sun, Feb 26, 2023 at 08:36:20PM +, Barry Scott wrote:
> > That's the new intended behavior. I you want non-debian python packages,
> > install them in a non-debian python via virtual environments.
>
> The idea is to prevent installing into /usr not preventing install in $USER I
> hope.
On Mon, Apr 10, 2023 at 11:29:25AM +0200, Robin ALEXANDER wrote:
> Hi,
>
> Let's assume I wish to maintain package_A across unstable and bullseye-
> backports. I understand from
> https://dep-team.pages.debian.net/deps/dep14/ that:
>
> 1. I need to create 3 branches in my git repository:
> -
On Mon, Apr 10, 2023 at 08:14:39PM +0200, Robin ALEXANDER wrote:
> In a nutshell, if I understood correctly the debian policy
>
> Branch debian/latest
> File debian/changelog will show "...(3.0.0-1) unstable ..."
>
> Branch debian/bullseye-backports
> File debian/changelog will show "...
On Tue, Jul 11, 2023 at 04:10:49PM +0200, Pierre Gruet wrote:
> I maintain a package that builds a shared library. I uploaded a new upstream
> version of it to Debian, with no removed symbols, no ABI change... Fine.
Tobias already explained that there was actually an ABI change, but...
> How
On Mon, Jul 10, 2023 at 01:19:38AM -0700, JOSE LUIS BLANCO CLARACO wrote:
> [2]. I attach the output of "dpkg -I" for the final binary package, where
> the "Depends: python3" is visible
No, as it says "phyton3".
(I would also expect that using appropriate substvars here is better than
writing
On Mon, Jul 10, 2023 at 11:22:05AM +0200, José Luis Blanco-Claraco wrote:
> On Mon, Jul 10, 2023 at 11:09 AM Andrey Rakhmatullin wrote:
> > No, as it says "phyton3".
> > (I would also expect that using appropriate substvars here is better than
> > writing deps m
On Mon, Jul 10, 2023 at 05:11:39PM +0200, José Luis Blanco-Claraco wrote:
> Thanks a lot, Andrey, for the time analyzing the problems here, and
> for the clarifications. I thought libpython was like "libc" for
> python...
It is, but as extensions are loadable plugins, they are fine with symbols
On Sat, Jul 15, 2023 at 09:01:19PM +0200, Ole Streicher wrote:
> Hi,
>
> I am upgrading one of my packages (iraf) to a new version. The new version
> comes with a "make install", which installs everything under /usr/lib/iraf/
> (and some other places).
>
> The "iraf" source package needs to
On Mon, May 29, 2023 at 01:24:12PM -0300, Tadeu Sampaio wrote:
> Thx Robin for the fast response! So what is needed in order to proceed with
> the ITP below, we need a sponsor?
Unless it's your ITP you should contact the current ITP owner so that you
don't make duplicate work.
On Fri, Jun 02, 2023 at 12:56:03PM +0200, Rock Storm wrote:
> I've been working on a small program to locally build packages in
> containers. Sort of an alternative to `pbuilder`. Because I find
> managing containers easier than managing base.tgz. In case anyone finds
> it useful as well, full
On Tue, Jun 20, 2023 at 05:15:05PM +0300, Ramūnas Keliuotis wrote:
> 1. Is it ok for source code to be in Github? or do I need a Salsa account?
It is OK for the source code to not have a VCS at all. It's also OK for
the packaging to not have a VCS at all, and these are two separate
questions, and
Control: retitle -1 RFS: lighttpd/1.4.70-1 -- light, fast, functional web server
On Sat, May 13, 2023 at 04:27:36AM -0400, Glenn Strauss wrote:
> (This is not actually an NMU, but a non-DD maintainer upload.)
If it's not a NMU it shouldn't be tagged as a NMU.
> Please help me to get lighttpd
On Tue, Dec 19, 2023 at 11:55:47PM +0100, Preuße, Hilmar wrote:
> sorry to bother again. I was requested to stop building package on i386
> (#1057407) so libqt6 can drop the i386 support too. So, how do do I do that?
> Do I have to specify (and maintain) the list of all supported arches in the
>
On Thu, Dec 14, 2023 at 04:53:50PM +0100, PICCA Frederic-Emmanuel wrote:
> I found this solution.
>
>
> execute_before_dh_missing-arch:
> # rm remaining files (workaround FTBFS...)
> rm -rf debian/tmp/usr/share
>
> execute_before_dh_missing-indep:
> # rm remaining files
On Sun, Dec 31, 2023 at 05:25:24PM +0100, Patrick ZAJDA wrote:
> First of all, I switched to the branch debian/stable/master where last
> bookworm backport is.
>
> Then I merged the tag debian/2.0.18-1 to have all commits until the version
> I wish to backport.
>
> Firstly, when running gbp dch
I see you added this tool to the list of similar tools on the wiki so you
at least know about that list. So how is your tool better than other tools
on that list, or at least than the ones packaged in Debian?
Please also note that if you followed the procedure outlined at
On Tue, Nov 21, 2023 at 04:39:42PM +, David James wrote:
> A couple of these dependencies have no version upstream. Is there a
> precedent for this? Can these dependencies be packaged?
There are definitely packages like that in Debian and the usual practice
is using date-based versions,
On Sat, Nov 11, 2023 at 07:36:07PM +0530, Shriram Ravindranathan wrote:
> dpkg-deb: building package 'libmagicenum-dev' in
> '../libmagicenum-dev_0.9.3-1_all.deb'.
[...]
> E: libmagicenum-dev: triplet-dir-and-architecture-mismatch is for arm64
> instead of all [usr/lib/aarch64-linux-gnu/]
So you
On Tue, Mar 12, 2024 at 07:25:56PM +0530, Shriram Ravindranathan wrote:
> Dear Mentors,
>
> Unfortunately, my SD card got corrupted (SD Card moment) and I do not have
> access to a sid environment right now. Is there a way to debootstrap a sid
> environment for packaging (from trixie perhaps)
On Tue, Mar 12, 2024 at 08:54:49PM +0530, Shriram Ravindranathan wrote:
> When I did a dist-upgrade from trixie it seemed to remove a bunch of
> necessary packages with error messages like this:
This is not my experience with a minimal debootstrapped chroot.
> Although just now I noticed there
On Mon, Mar 25, 2024 at 11:57:19AM +0530, Shriram Ravindranathan wrote:
> Dear Mentors,
>
> I noticed from the past couple of days, uscan seems to be having trouble
> finding files from the gitlab tags page.
>
> ```
> $ uscan
> uscan warn: In debian/watch no matching files for watch line
>
On Sat, Mar 30, 2024 at 03:32:53PM -0400, Qianqian Fang wrote:
> info: Hint: make sure the version in debian/changelog matches the unpacked
> source tree
You should do this.
> for pybj, ci tasks finished ok, but the test-crossbuild-arm64 job failed
>
>
Control: tags -1 + moreinfo
Some issues found after a quick review:
- There are many issues listed by lintian such as outdated compat level,
outdated Standards-Version, an issue with the short description, missing
Rules-Requires-Root.
- There should be only one changelog entry, and in
Control: tags -1 + moreinfo
There are quite a lot of issues reported by lintian so you should fix at
least those before looking for sponsorship. The biggest problem is
debian/changelog.
Please remove the moreinfo tag after these are addressed.
--
WBR, wRAR
signature.asc
Description: PGP
Control: tags -1 + moreinfo
On Fri, Dec 15, 2023 at 03:36:19PM -0500, Patrik Dufresne wrote:
> dget -x
> https://mentors.debian.net/debian/pool/main/r/rdiffweb/rdiffweb_2.8.7.dev41+g849af0c+dfsg-1.dsc
>
> Changes for the initial release:
>
> rdiffweb (2.8.7.dev41+g849af0c+dfsg-1) unstable;
Control: tags -1 + moreinfo
Control: retitle -1 RFS: bash-unit/2.1.0-1 [ITP] -- bash_unit - bash unit
testing
Some issues found after a quick review:
- The package should be arch:all and shouldn't use ${shlibs:Depends}.
- The GPL-3 snippet in d/copyright looks wrong.
- The upstream docs should
I have several suggestions for this:
- Can you provide debian/watch? It should be possible.
- debian/k3conf.1 has a *roff warning, lintian also catches it.
--
WBR, wRAR
signature.asc
Description: PGP signature
Control: tags -1 + moreinfo
The package FTBFS: /bin/bash: line 1: /usr/bin/python3: No such file or
directory
Also, debian/watch is empty but present and I'm not sure about
__AUTO_PERMISSIVE__ and __UNKNOWN__ in debian/copyright.
--
WBR, wRAR
signature.asc
Description: PGP signature
Control: tags -1 + moreinfo
You should provide a separate -dev package, currently the development
files are shipped in the library package.
There is a hardcoded Depends: libkrb5-3, why is this needed?
There are unused files in debian/, such as libsmb2-dev.* and libsmb21.*.
You should remove the
Control: tags -1 + moreinfo
Some issues found after a quick review:
- It should have only one changelog entry.
- Pre-built libclang_rt.builtins-wasm32.a should be removed from the
orig.tar, assuming it's not used in the build process.
- debian/rules hardcodes llvm-*-16 and clang-16 but B-D are
Control: tags -1 + moreinfo
The shared libraries don't have versioned SONAMEs and so shouldn't be
packaged as such until/unless the upstream fixes that or, if the upstream
cannot or doesn't want to keep ABI stable, they should be packaged in the
way that ensures that the dependencies track this
Control: tags -1 + moreinfo
This FTBFS: "! LaTeX Error: File `lmodern.sty' not found."
Also I think the additional notes in the changelog entry belong in
README.Debian or README.source.
--
WBR, wRAR
signature.asc
Description: PGP signature
Control: tags -1 + moreinfo
$(MAKE) clear (as a replacement for $(MAKE) clean) should run in
override_dh_auto_clean, not override_dh_clean.
debian/watch is empty.
There is a commented out override_dh_auto_configure.
002-add-fortify-flags.patch adds -D_FORTIFY_SOURCE=2 explicitly, but the
proper
Control: tags -1 + moreinfo
> The latest release of hyprland-protocols is v0.2 which is behind by a few
> commits.
Then the upstream version should be >> 0.2, e.g, 0.2+20230811, not << 0.2
as it is now.
Also, as the package is arch:all it shouldn't use ${shlibs:Depends} (which
will be emoty
On Fri, Apr 05, 2024 at 08:53:58PM +, Martin Dosch wrote:
> Dear Andrey,
>
> thank you for the valuable feedback. I hope it is all properly settled now.
> I just uploaded a new build to mentors and pushed the changes to the repo.
Hi Martin, you added a B-D on itself, I assume it's to run
On Sat, Apr 06, 2024 at 02:14:11PM +, Martin Dosch wrote:
> > Hi Martin, you added a B-D on itself, I assume it's to run build-time
> > tests, buit the idea of build-time tests is to use the software being
> > package,
>
> Do you know how to achieve this? When I remove the build-dep on itself
On Fri, Mar 29, 2024 at 12:52:03PM +0530, Shriram Ravindranathan wrote:
> * Vcs : https://salsa.debian.org/debian/keep
This doesn't exist.
--
WBR, wRAR
signature.asc
Description: PGP signature
On Wed, Apr 10, 2024 at 12:39:47PM -0500, Andrew Davis wrote:
> > - debian/k3conf.1 has a *roff warning, lintian also catches it.
> >
>
> I don't see this warning,
W: k3conf: groff-message error: automatically ending diversion
'an*link-text-div' on exit [usr/share/man/man1/k3conf.1.gz:3]
Are
On Wed, Apr 10, 2024 at 03:05:04PM -0500, Andrew Davis wrote:
> is that not right? Maybe my lintian version is old, I'm on v2.114, I'll
> see if updating that helps.
2.114 is older than stable, and for packages aimed at unstable you need
to use tools from unstable.
--
WBR, wRAR
signature.asc
On Mon, Apr 15, 2024 at 01:25:05AM +0530, Alan M Varghese wrote:
> > This FTBFS: "! LaTeX Error: File `lmodern.sty' not found."
>
> lmodern.sty comes from the package `lmodern`. This package should be
>
> installed (as a transitive dep) when 'texlive-fonts-extra' is installed.
No, see below. But
On Thu, Apr 18, 2024 at 02:43:23AM +, Nilson Silva wrote:
> Hey!
> The purpose of this email is to contribute to the recent changes that
> occurred in Gitlab with its
> HTML that caused a series of errors in tracking new versions.
>
> Reading the wiki more specifically at this point:
>
On Sat, May 04, 2024 at 03:44:45AM +, james smith wrote:
> I am trying to package ly[1] I got everything up to the rules part, I am
> stuck thinking on how to edit/make the makefile, if you have any tips or
> tools that can make this a easier process, I would be much grateful
You don't
Control: tags -1 + moreinfo
On Fri, May 24, 2024 at 05:35:00PM +0200, Julius Pfrommer wrote:
> To access further information about this package, please visit the following
> URL:
>
> https://mentors.debian.net/package/open62541/
If you didn't run lintian locally (which you should), please
Control: tags -1 + moreinfo
On Sat, May 25, 2024 at 08:20:43AM +0200, Joachim Zobel wrote:
> To access further information about this package, please visit the
> following URL:
>
> http://www.heute-morgen.de/debian/repo/unstable/main/source/net/
>
> Alternatively, you can download the package
59 matches
Mail list logo
