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 Opendigitalr
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 st
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:
> - upst
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 "... (3.0.0-1
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 1.4.
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 info
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 p
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 deps
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
bei
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 shoul
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 divid
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 the
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 https://g
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 d
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 ~/.pbui
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
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, 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, probabl
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 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
> de
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
https://mentors.debian.ne
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) whil
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 are
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
> htt
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 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
>
> https://salsa.debian.org/science-team/pybj/-
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; u
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
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 general
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 signa
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 b
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 AB
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 .l
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 build
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 anyw
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 fi
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 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 yo
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
De
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:
> http
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 normally
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 visi
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 wi
Control: tags -1 + moreinfo
You shouldn't close the RFS in the changelog entry, you are expected to
have an ITP and close it there.
You should use the latest debhelper compat level.
Why are you modifying the SONAME, and why are you doing it with patchelf?
You should put the packaging repo, not the
On Tue, May 28, 2024 at 03:52:57PM +0200, Julius Pfrommer wrote:
> > Why are you modifying the SONAME, and why are you doing it with patchelf?
>
> The intent was to do the SONAME patching entirely in the rules file.
> Now we instead ship a small patch to the upstream CMakeLists.txt that
> modifie
On Tue, May 28, 2024 at 05:48:10PM +0200, Julius Pfrommer wrote:
> > > The intent was to do the SONAME patching entirely in the rules file.
> > > Now we instead ship a small patch to the upstream CMakeLists.txt that
> > > modifies the linker flags.
> > This doesn't answer why are you changing the
On Mon, Jun 10, 2024 at 12:58:01PM +0200, Lorenzo wrote:
> > If I wish to create two binary packages with different
> > configurations from a single source package (e.g. to support
> > different ISA levels), what's the best way to implement this?
>
> I'm not sure I understand, you want the same bi
On Tue, Jun 11, 2024 at 07:09:15PM +, David James wrote:
> These examples were exactly what I needed, thank you both. One more
> thing: When running a package builder such as dpkg, does dh run once
> for each item in DEB_BUILD_PROFILES?
Are you really asking about DEB_BUILD_PROFILES? Because I
On Sun, Jun 30, 2024 at 10:39:06AM +0200, lorenzo wrote:
> Dear Mentors,
>
> in runit, services are defined as directories with files inside and
> I'm not sure what exactly can or can't be done when a package has to
> purge a service:
>
> if the service is below /etc, files provided by the packag
On Sun, Jun 30, 2024 at 08:08:58PM +0200, lorenzo wrote:
> > > if the service is below /etc, files provided by the package can
> > > be removed even if modified,
> >
> > Normally no.
> >
> > > but the directory can't be removed if there are extra files inside.
> > > Correct?
> >
> > Just leave t
On Sun, Jun 30, 2024 at 08:56:59PM -0700, Kayven Riese wrote:
> I'm the guy with the hokey cut -m thing. It was my friend's idea, and if I
> would have tried a bit harder it would have occurred to me that an
> additional POSIX pipe would accomplish the task. My friend keeps telling
> me he got so
On Thu, Jul 04, 2024 at 07:55:03AM -0300, Jeremy Theler wrote:
> I'm pretty much in the same position.
>
> There is an RFP bug report at
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068648
> but got no response.
This is expected for RFPs. RFPs are "I want someone to package this" and
thu
On Thu, Jul 04, 2024 at 01:22:29PM +0200, Daniel Gröber wrote:
> > I'm pretty much in the same position.
> >
> > There is an RFP bug report at
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068648
> > but got no response.
>
> RFP means "someone else please do this", you need to file an R
On Thu, Jul 04, 2024 at 02:04:01PM +0200, Daniel Gröber wrote:
> On Thu, Jul 04, 2024 at 04:30:43PM +0500, Andrey Rakhmatullin wrote:
> > You don't need to CC debian-mentors on ITPs, you don't use ITPs to ask for
> > sponsorship and RFSes are sent to debian-mentors
On Thu, Jul 04, 2024 at 03:22:35PM +0200, Daniel Gröber wrote:
> > > It's complicated^{TM}. The sponsorship docs don't actually guide people on
> > > how to get others interested in their work
> >
> > I don't think this is necessary or helpful: most RFSes are sponsored
> > because they are in a go
On Fri, Jul 12, 2024 at 05:54:59AM +0100, Phil Wyett wrote:
> Morning all,
>
> As we embark on a new process where packages submitted to mentors are reviewed
> and brought to a "Ready" stage for then busy DDs who are gracious enough to
> give
> their time to review and possibly sponsor into Debia
On Wed, Jul 17, 2024 at 10:20:38AM -0400, Adam Danischewski wrote:
> Thanks for the quick response - yes I'd like to add the package to Debian.
> I have actually packaged it, but I really wasn't sure how the system
> worked.
Please look at https://mentors.debian.net/intro-maintainers/ to learn the
On Tue, Jul 23, 2024 at 04:37:18AM +0100, Phil Wyett wrote:
> > > Should we require all submissions to mentors file an RFS?
> > >
> > > Please discuss. :-)
> >
> > IMHO The existing documentation advocates already on using RFS bugs:
> >
> > https://mentors.debian.net/sponsors/rfs-howto/
> > "In
On Thu, Aug 01, 2024 at 08:18:04AM +0300, Tommi Höynälänmaa wrote:
> Hello
>
> Packages theme-d and theme-d-intr are to be autoremoved from testing on
> August 30. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074756. I
> think that this bug is a bug in guile and not in theme-d and I have
On Sun, Aug 04, 2024 at 01:40:16PM +, Kilian Romberg wrote:
> I'm looking to include already existing Debian packaging for the
> LibreWolf browser (instructions on how to obtain at
> https://codeberg.org/librewolf/bsys5) in the Debian repositories.
This doesn't have any Debian packaging as it
On Wed, Aug 07, 2024 at 03:25:25PM +0200, PICCA Frederic-Emmanuel wrote:
> Hello, I am trying to write a watch file for Fiji
>
> All the version are available in this
>
> https://downloads.imagej.net/fiji/archive/@ANY_VERSION@/fiji-linux64.zip
Where is the HTML page that lists these that uscan
On Wed, Aug 07, 2024 at 03:52:12PM +0200, PICCA Frederic-Emmanuel wrote:
> i just need to download
>
> https://drive.switch.ch/index.php/s/WOVSIPMky2JsXsp/download
[...]
> Is it possible to ask for uncoditionnal download ?
I don't think uscan is useful for this.
--
WBR, wRAR
signature.asc
D
On Thu, Aug 08, 2024 at 02:47:52PM +0200, PICCA Frederic-Emmanuel wrote:
> the python-pyepics depends on the libca-dev and libcom-deb provided by
> epics-base.
>
> The upstream hardcode the version of the API in the library name and so in
> the binary package name
>
> ii libca4.14.4:amd64
On Fri, Aug 09, 2024 at 11:00:27AM +0200, PICCA Frederic-Emmanuel wrote:
> > The best way to get dependencies on shared libraries is of course
> > dpkg-shlibdeps, but I assume there is a reason it's not used here so you
> > should explain why.
>
> Yes but this a python binding which use ctypes, so
On Wed, Aug 28, 2024 at 08:35:06AM +, dblmr wrote:
> So then I decided to forge ahead. I found the latest orphaned package, which
> was
>
> png23d
>
> and installed it, which seemed to work, maybe. I got the following:
>
> Processing triggers for man-db (2.11.2-2) ...
> == How can you h
On Sun, Sep 01, 2024 at 12:58:21PM +0200, Patrick ZAJDA wrote:
> Hello,
>
> I maintain pidgin-skype, which depend on telepathy-haze.
> telepathy-haze has been removed from testing due to #1075560 so Pidgin-Skype
> is also removed.
>
> It looks this package has not been updated since 2022.
>
> Wh
On Thu, Sep 05, 2024 at 12:20:54PM +0200, Lorenzo wrote:
> I would like to upload a package to mentors targeting experimental,
> however:
>
> my existing experimental chroot is broken beyond repair after
> sbuild-update; when I try to create a new one I get
>
> # # sbuild-createchroot experiment
On Tue, Sep 10, 2024 at 07:22:01AM +0300, Tommi Höynälänmaa wrote:
> Hello
>
> In https://wiki.debian.org/binNMU it says that declaring dependency between
> an arch: all to an arch: any package should be done by "Depends: foo (>=
> ${source:Version}), foo (<< ${source:Version}.1~)". What is the pu
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 package
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 (notabl
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 directo
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 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 tar.xz
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
> > > projec
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 fr
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.
Yo
On Tue, Oct 15, 2024 at 04:27:27PM +0800, EiPiFun wrote:
> The problem is that its GitHub release does not contains all files.
> You can check the file:
> https://github.com/googleapis/google-cloud-python/archive/refs/tags/google-ai-generativelanguage-v0.6.10.tar.gz
I did, and at first I thought y
On Tue, Oct 15, 2024 at 05:31:23PM +0800, EiPiFun wrote:
> > I did, and at first I thought you are only looking at the top level
> > instead of looking at the module directory, but your PR edits a file
> > in there so I'm confused.
>
> Yeah, I forget to remind you that Google uses a large mono re
On Tue, Oct 15, 2024 at 03:15:50PM +0800, EiPiFun wrote:
> Hello, Mr.Phil Wyett!
>
> Thanks for your reminds.
>
> Its GitHub release lacks setup.py or pyproject.toml
It doesn't lack setup.py though?
> I start a small pull request to inform them they should add docs info.
>
> https://github.co
On Fri, Oct 11, 2024 at 02:36:54PM +0200, souravbhattacha...@tutamail.com wrote:
> I am aware of the issue related to the CI failure. Tests runs fine on my
> pc,
Then you aren't testing in a minimal environment.
> The error is most likely due to the absence of tenacity in the
> host itself.
Sure
On Thu, Oct 03, 2024 at 11:02:42PM -0400, stev...@osfda.org wrote:
> Sounds like you know what you're doing. So I have a couple of QUICK
> questions on deb policy, if you wouldn't mind answering them. [I searched
> for an answer, but the advice was a bit contested...]
>
> * There's /usr/local/sha
On Wed, Oct 16, 2024 at 10:57:42AM +0200, Lorenzo wrote:
> Hello mentors,
>
> mplayer 2:1.5+svn38638-1 was uploaded on experimental with fixes for
> gcc-14; however it still fails on s390x[1]: it is my understanding that
> the build need to be fixed there in order to release mplayer in trixie.
> I
On Wed, Oct 16, 2024 at 01:57:20PM +0200, Lorenzo wrote:
> > mplayer is not in testing so it can migrate even without the s390x
> > binary as far as I know.
>
> humm, fine for me although I'm not sure I completely understand the
> logic (mplayer:s390x is in stable and unstable right now, so
> remo
On Thu, Oct 10, 2024 at 08:11:58AM +0200, Andreas Tille wrote:
> I was a happy user of pristine-tar for >10 years but since some time
> (about 2 months) I end up with brocken tarball checksums when doing `gbp
> buildpackage` in *every* case.
Does it actually use pristine-tar?
--
WBR, wRAR
si
On Thu, Oct 10, 2024 at 04:33:38PM +0200, Andreas Tille wrote:
> > > I was a happy user of pristine-tar for >10 years but since some time
> > > (about 2 months) I end up with brocken tarball checksums when doing `gbp
> > > buildpackage` in *every* case.
> >
> > Does it actually use pristine-tar?
On Thu, Oct 10, 2024 at 05:49:13PM +0200, Andreas Tille wrote:
> > > Ah, well, that was the trigger I needed. Usually I had
> > >
> > >pristine-tar = True
> >
> > I hold the strong opinion that this is bad and repos using pristine-tar
> > should have pristine-tar=True in debian/gbp.conf.
On Thu, Oct 10, 2024 at 05:32:13PM +0200, Andreas Tille wrote:
> > Whats the output of
> > cat ~/.gbp.conf
>
> Ah, well, that was the trigger I needed. Usually I had
>
>pristine-tar = True
I hold the strong opinion that this is bad and repos using pristine-tar
should have pristine-tar=T
On Thu, Oct 10, 2024 at 07:37:41PM +0500, Andrey Rakhmatullin wrote:
> > > > I was a happy user of pristine-tar for >10 years but since some time
> > > > (about 2 months) I end up with brocken tarball checksums when doing `gbp
> > > > buildpackage` in *every
On Sun, Oct 27, 2024 at 07:42:46PM +0900, Daichi Fukui wrote:
> I'm writing to seek your guidance on backporting a fix for CVE-2021-45463
> to the Bullseye release. I've successfully developed a fixed version of
> gegl for Bullseye, but I'm facing a roadblock due to the age of the
> Bullseye releas
On Mon, Nov 11, 2024 at 01:43:19PM +, Aaron Boxer wrote:
> Dear Mentors,
>
> I have uploaded my latest package here:
> https://mentors.debian.net/package/libgrokj2k/
> I would greatly appreciate help uploading the package to unstable
Please use the RFS mechanism.
--
WBR, wRAR
signature.as
On Mon, Nov 11, 2024 at 03:45:51PM +, Aaron Boxer wrote:
> Hi Andrey,
>
> Thanks, I do have a sponsor, just have not had a response from him.
Then you should use the RFS mechanism.
--
WBR, wRAR
signature.asc
Description: PGP signature
On Sun, Sep 29, 2024 at 06:55:15PM +0200, Markus Blatt wrote:
> if a package was part of the t64 transition then the library now has
> a t64 suffix added.
>
> How should one proceed if there is a new version of that software that needs
> a bump in the soversion. Should I keep the t64 suffix or dro
1 - 100 of 131 matches
Mail list logo
