Re: HELP: Fixing a debconf bug in proftpd

On 28.11.2016 21:24, Hilmar Preuße wrote: Hi, > we got bug #820984 on debconf a while ago. I'm not very familiar w/ > debconf, hence I had a look into the templates/config delivered w/ > debconf itself. > I'm my eyes the code in proftpd is about a 1:1 copy of the code in > debcon

Re: copyright-contains-dh_make-todo-boilerplate

Am 09.02.2017 um 11:30 tastete Narcis Garcia: Hi, This Lintian result is an error*:* E: ntfsundelete-tree: copyright-contains-dh_make-todo-boilerplate And I don't find any documentation about this message. This is the copyright file:

HELP: Fixing a debconf bug in proftpd

Hi, we got bug #820984 on debconf a while ago. I'm not very familiar w/ debconf, hence I had a look into the templates/config delivered w/ debconf itself. I'm my eyes the code in proftpd is about a 1:1 copy of the code in debconf, nevertheless it does not work as expected. 1. Would anybody

Re: Access to Porter machines as Debian Maintainer?

Am 29.04.2019 um 19:45 teilte Mattia Rizzolo mit: Hi, Done! username: hilmar-gu...@users.alioth.debian.org → hill...@debian.org Please confirm it works for you :) Worked. Many thanks! For the porter boxes I've opened

Re: Access to Porter machines as Debian Maintainer?

Am 29.04.2019 um 13:41 teilte Mattia Rizzolo mit: On Sun, Apr 28, 2019 at 08:52:13PM +0200, Hilmar Preuße wrote: Hi Mattia, I tried already to use the claim interface, but I'm pretty sure this did not give the expected results. Therefore I'll try to fix the match and then try to get access

Re: Access to Porter machines as Debian Maintainer?

On 27.04.19 03:22, Paul Wise wrote: > On Sat, Apr 27, 2019 at 3:11 AM Hilmar Preuße wrote: Hi, >> "You are currently logged in with SSO username , but you cannot be >> matched to any person in the site. >> If you are already in the site, for example as a Debian

Re: Access to Porter machines as Debian Maintainer?

On 27.04.19 03:27, Paul Wise wrote: Hi, > Since you are not a Debian member, that address is not to be used. > The welcome mail you got from DSA should have made that clear. > I'm not aware of any welcome mail I should have received. Not sure, to which address it was sent, but the LDAP entry

Re: Access to Porter machines as Debian Maintainer?

On 28.04.19 03:46, Paul Wise wrote: > On Sun, Apr 28, 2019 at 5:34 AM Hilmar Preuße wrote: Hi, >> I'm not aware of any welcome mail I should have received. > > No idea what went wrong but the template for it is here: > > https://salsa.debian.org/dsa-team/mirror/us

Re: Access to Porter machines as Debian Maintainer?

Am 28.04.2019 um 09:35 teilte Mattia Rizzolo mit: On Sat, Apr 27, 2019 at 11:33:53PM +0200, Hilmar Preuße wrote: Hi, I'm not aware of any welcome mail I should have received. Not sure, to which address it was sent, but the LDAP entry lists my web.de address, which is correct. I simply

Re: Access to Porter machines as Debian Maintainer?

On 26.04.19 12:59, Paul Wise wrote: Hi Paul, > Each time you want to access a new host or renew existing access, go > through the procedure again. Docs are here: > > https://dsa.debian.org/doc/guest-account/ > I tried this too. The page told me I should go to the "the New Members site." [1]

Re: Access to Porter machines as Debian Maintainer?

On 26.04.19 21:11, Hilmar Preuße wrote: Hi Paul, > "You are currently logged in with SSO username , but you cannot be > matched to any person in the site. > If you are already in the site, for example as a Debian Maintainer, you > can try to correct the situation using th

Re: Access to Porter machines as Debian Maintainer?

On 26.04.19 21:11, Hilmar Preuße wrote: Hi, > "You are currently logged in with SSO username , but you cannot be > matched to any person in the site. > If you are already in the site, for example as a Debian Maintainer, you > can try to correct the situation using the claim inte

Upload of texinfo-doc-nonfree?

Hi all, I'm trying to upload new release of texinfo-doc-nonfree to Debian. My first upload was rejected, b/c I made a source-only upload and forgot to set the "XS-Autobuild: yes" in debian/control. Next try was w/ that field and last try w/o that field but binary upload (as that package just

Access to Porter machines as Debian Maintainer?

Hi all, since a few days ago I am "Debian Maintainer, with guest account". Now I'm trying to log in into a porter box to investigate build failures. On [1] is written, I should do this on the "New Members site". If I open from here page [2] I get the info "As a Debian Maintainer, with guest

Re: Access to Porter machines as Debian Maintainer?

On 25.04.19 15:31, Mo Zhou wrote: Hi Mo, > I'm sure a "DM with guest account" can access the porter boxes because > I've ever done so. You have to wait for some time because the machines > need to sync LDAP information. > So, what means "some time"? My LDAP Account was created / changed finally

Re: Access to Porter machines as Debian Maintainer?

On 26.04.19 06:13, Mattia Rizzolo wrote: > On Fri, 26 Apr 2019, 4:48 am Paul Wise, wrote: >> On Thu, Apr 25, 2019 at 6:11 PM Hilmar Preuße wrote: Hi Paul, hi Mattia, >>> Unfortunately, that does not work. Because I suspect rather an >>> organizational, than a technic

Re: Gathering debug data from buildd's?

Am 25.07.2019 um 16:39 teilte Frédéric Bonnard mit: > On Thu, 25 Jul 2019 15:35:31 +0200, Hilmar Preuße wrote: Hi, >> Is it possible to force a rebuild after updating build tools on the >> builders? > > yes, see last paragraph here : > https://release.debian.org/w

Re: Gathering debug data from buildd's?

Am 31.07.2019 um 09:46 teilte Frédéric Bonnard mit: Hi Frédéric, >> I sent a request 3 days ago, still no response. Do I have to sign my >> E-Mail to get the request processed? > > No. It just takes a bit of time sometimes for people of the team that > do this manually but they usually answer,

Gathering debug data from buildd's?

Hi, dumb question: since a few releases we have problems to build a package on ppc64 [1]. The resulting binary segfaults when generating files. I reported the problem upstream: they asked me for core dumps/gdb output. How to proceed: I could try to get access to a porter box through an RT

Re: Gathering debug data from buildd's?

On 24.07.19 11:05, Frédéric Bonnard wrote: Hi Frédéric, > potentially recreate the issue in a ppc64 vm ? > I may also try to reproduce in a vm I already have. > Well, I don't have an ppc64 at hand and I'm not really willing to run every possible arch on my own hardware. If it would be quite

Re: Gathering debug data from buildd's?

On 24.07.19 14:36, Andrey Rahmatullin wrote: Hi, > This exact command mostly worked for me. It failed later, with > "powerpc-utils depends on pmac-utils; however: Package pmac-utils is not > installed." > Correct: #927255 H. -- sigfault #206401 http://counter.li.org signature.asc

Re: Gathering debug data from buildd's?

On 24.07.19 14:36, Andrey Rahmatullin wrote: > On Wed, Jul 24, 2019 at 02:04:29PM +0200, Hilmar Preuße wrote: Hi, >> qemu-debootstrap --verbose --arch=ppc64 >> --keyring=/usr/share/keyrings/debian-ports-archive-keyring.gpg sid ppc64>> >> http://ftp.de.debian.org/de

Re: Gathering debug data from buildd's?

On 24.07.19 11:21, Andrey Rahmatullin wrote: > On Wed, Jul 24, 2019 at 11:13:59AM +0200, Hilmar Preuße wrote: Hi, >> Well, I don't have an ppc64 at hand and I'm not really willing to run >> every possible arch on my own hardware. If it would be quite easy to >> emulate an pp

Re: Gathering debug data from buildd's?

On 24.07.19 13:06, Hilmar Preuße wrote: Hi, > I'll try further. > Next try: qemu-debootstrap --verbose --arch=ppc64 --keyring=/usr/share/keyrings/debian-ports-archive-keyring.gpg sid ppc64 http://ftp.de.debian.org/debian-ports/ I: Running command: debootstrap --arch ppc64 --foreign --v

Re: Upload of texinfo-doc-nonfree?

On 14.07.19 17:07, Hilmar Preuße wrote: Hi, > I'm trying to upload new release of texinfo-doc-nonfree to Debian. My > first upload was rejected, b/c I made a source-only upload and forgot to > set the "XS-Autobuild: yes" in debian/control. > > Next try was w/ th

Re: Gathering debug data from buildd's?

On 24.07.19 11:05, Frédéric Bonnard wrote: Hi Frédéric, > potentially recreate the issue in a ppc64 vm ? > I may also try to reproduce in a vm I already have. > Were you successful in problem reproduction? Hilmar -- sigfault #206401 http://counter.li.org signature.asc Description: OpenPGP

Re: Gathering debug data from buildd's?

On 24.07.19 11:21, Andrey Rahmatullin wrote: > On Wed, Jul 24, 2019 at 11:13:59AM +0200, Hilmar Preuße wrote: Hi, >> Well, I don't have an ppc64 at hand and I'm not really willing to run >> every possible arch on my own hardware. If it would be quite easy to >> emulate an pp

Re: Gathering debug data from buildd's?

Am 25.07.2019 um 13:15 teilte Frédéric Bonnard mit: Hi *, no I didn't reproduce the issue in a ppc64 vm even after 3 tries. Maybe it was an gcc bug, which has been solved in the meantime? The builder used gcc-8.3.0-7, meanwhile I (and probably you too) used gcc-8.3.0-19. Is it possible to

Re: E: dvisvgm: possible-gpl-code-linked-with-openssl

Am 21.09.2019 um 12:22 teilte Andrey Rahmatullin mit: > On Sat, Sep 21, 2019 at 12:00:48PM +0200, Hilmar Preuße wrote: Hi, >> in [1] I changed the BD of dvisvgm from ghostscript to libgs-dev (BD on >> gs was removed later on), due to #940700. The package still compiles >>

E: dvisvgm: possible-gpl-code-linked-with-openssl

Hi, in [1] I changed the BD of dvisvgm from ghostscript to libgs-dev (BD on gs was removed later on), due to #940700. The package still compiles fine, but lintian now moans: E: dvisvgm: possible-gpl-code-linked-with-openssl Indeed the new package now depends on libssl1.1 and the binary is

Re: proftpd-dfsg not migrating

Am 04.11.2019 um 10:05 teilte Andrey Rahmatullin mit: > On Sun, Nov 03, 2019 at 11:48:24PM +0100, Hilmar Preuße wrote: Hi, >> just a dumb question: https://tracker.debian.org/pkg/proftpd-dfsg shows >> that the latest upload did not migrate to testing yet. The excuses list >

proftpd-dfsg not migrating

Hi, just a dumb question: https://tracker.debian.org/pkg/proftpd-dfsg shows that the latest upload did not migrate to testing yet. The excuses list does not show me, why not. Can anybody explain, why the latest upload did not reach buster yet? Hilmar -- sigfault #206401 http://counter.li.org

Re: proftpd-dfsg not migrating

Am 04.11.2019 um 16:57 teilte Mattia Rizzolo mit: > On Mon, Nov 04, 2019 at 04:54:07PM +0100, Hilmar Preuße wrote: Hi, >> Thanks for the pointer! As the 1.3.6a probably does not contain an API >> change I'll revert the API version change in the Debian package...and >> packa

Re: proftpd-dfsg not migrating

Am 03.11.2019 um 23:48 teilte Hilmar Preuße mit: Hi, > just a dumb question: https://tracker.debian.org/pkg/proftpd-dfsg shows > that the latest upload did not migrate to testing yet. The excuses list > does not show me, why not. > > Can anybody explain, why the latest uploa

Bug#952961: RFS: netsend/0.0~svnr250-1.3 [NMU, RC] -- a speedy filetransfer and network diagnostic program

On 3/2/20 1:05 PM, Sudip Mukherjee wrote: > I am looking for a sponsor for my package "netsend" > > * Package name: netsend >Version : 0.0~svnr250-1.3 >Upstream Author : Hagen Paul Pfeifer, Florian Westphal > * URL : http://netsend.berlios.de/ > I have doubt,

Help: Building asymptote on alpha

Hi, I'm trying to build package asymptote on alpha. Currently it does not build on "official" builders due to missing BD's. Therefore I use qemu to build inside an alpha chroot on a x64 Virtualbox. The build log is here: https://paste.debian.net/1126163/. This "GC Warning: Out of memory -

Re: Help: Building asymptote on alpha

Am 16.01.2020 um 17:24 teilte Matthew Fernandez mit: Hi, > This error appears to be from the BDW garbage collector [0]. Are you > sure it works on Linux on Alpha? The docs refer to a missing file, > README.alpha, and the source has exciting comments like “untested but > hopefully should work on

Re: Help: Building asymptote on alpha

Am 16.01.2020 um 03:31 teilte Ko Ko Ye` mit: > use swap or tune ram ?? > Otherwise may I test for you ?. > Do you have an alpha CPU @hand? If there would be RAM pressure I'd expect that top shows me high RAM utilization, which is not the case. I guess, the idea of Matthew Fernandez sounds

sbuild & cross build

Hi, I'm pretty sure this is a dumb question. I'm using sbuild to cross compile packages, e.g. texlive-bin. This works fine for release arches. Now I try to build for a non-release arch like this: sbuild --host=sparc64 -d unstable --extra-repository='deb http://ftp.de.debian.org/debian-ports

Re: sbuild & cross build

Am 15.04.2020 um 02:45 teilte Wookey mit: > On 2020-04-15 00:02 +0200, Hilmar Preuße wrote: Hi, Thanks for the answer Wookey! >> I'm pretty sure this is a dumb question. I'm using sbuild to cross >> compile packages, e.g. texlive-bin. This works fine for release arches. >&g

Bug#955496: RFS: libsys-hostaddr-perl/0.993-1 [ITP] -- Get IP address information about this host

Am 05.04.2020 um 22:20 teilte Adam Borowski mit: > On Wed, Apr 01, 2020 at 05:51:28PM +0200, Hilmar Preusse wrote: Hi, >> * Package name: libsys-hostaddr-perl >>Version : 0.993-1 >>Upstream Author : Jeremy Kister|http://jeremy.kister.net/ >> * URL :

Re: sbuild & cross build

Am 18.04.2020 um 16:42 teilte Niels Thykier mit: Hi Niels, >> W: texlive-bin source: debian-rules-sets-DEB_BUILD_OPTIONS line 68 >> >> I also tried "MAKEFLAGS += -j8" inside the if statement, but the option >> was ignored. >> >> How do I implement the Debian way? Thanks! >> > Have you tried to

Re: Again question about migration to testing

Am 24.04.2020 um 06:21 teilte Sebastiaan Couwenberg mit: > On 4/24/20 12:01 AM, Hilmar Preuße wrote: Hi Sebastiaan, >> I'm quite sure, this regression is not caused by the TL upload, but by >> the Sphinx upload. The last successful autopkgtest was with version >> Sphinx v

Again question about migration to testing

Hi, the TeX Live packages do not migrate to testing, although there is no RC bug and they are old enough. The only reason I see is: autopkgtest for jupyter-sphinx-theme/0.0.6+ds1-9: amd64: Regression ♻ , arm64: Regression ♻ I'm quite sure, this regression is not caused by the TL upload, but by

Bug#960477: RFS: iptux/0.7.6-2 -- Intranet communication tool for Linux

Control: merge -1 960475 Am 13.05.2020 um 06:29 teilte 铜豌豆 Linux mit: > Package: sponsorship-requests > Severity: normal > > Dear mentors, > > I am looking for a sponsor for my package "iptux" > I guess this one is identical to #960475. Merging. H. -- sigfault #206401 http://counter.li.org

Bug#969446: RFS: vguitar-2.6 [ITP] -- Play Guitar in any term window. Use with a MIDI synthesizer (qsynth).

Am 11.09.2020 um 03:18 teilte Nick Strauss mit: Hi Nick, >> Don't install a program into /usr/local. The package won't be accepted. > > My makefile has prefix defined for vguitar exe destination. > > ./Makefile:prefix = /usr/local > ./Makefile:$(DESTDIR)$(prefix)/bin/vguitar > > What

Bug#969446: RFS: vguitar-2.6 [ITP] -- Play Guitar in any term window. Use with a MIDI synthesizer (qsynth).

Am 08.09.2020 um 04:09 teilte Nick Strauss mit: Hi, >>   Please review each of those files and make sure that unnecessary >> template placeholders are not included in your packaging debian/ dir. >> Please pay special attention to the debian/copyright file since it was > > I have manually

Bug#969446: RFS: vguitar-2.6 [ITP] -- Play Guitar in any term window. Use with a MIDI synthesizer (qsynth).

Am 09.09.2020 um 19:27 teilte Hilmar Preuße mit: Hi, > Build the package fails nevertheless b/c vguitar binary is installed > into usr/local/. Did you even try to build a binary package from your > source package? > Attached is a debian.tar.gz you could use as starter. You still n

Bug#969446: RFS: vguitar-2.6 [ITP] -- Play Guitar in any term window. Use with a MIDI synthesizer (qsynth).

Am 10.09.2020 um 05:44 teilte Nick Strauss mit: Hi, Did you get the updated debian.tar.xz I sent you? Consider to use that one. > I added build dependencies (BD):> > Build-Depends: >  debhelper (>=9),>   > libncurses5-dev,>  libasound2-dev,>  libc6-dev> libc6-dev is pulled in by

Bug#969446: RFS: vguitar-2.6 [ITP] -- Play Guitar in any term window. Use with a MIDI synthesizer (qsynth).

Am 12.09.2020 um 05:24 teilte Nick Strauss mit: Hi, >> The tar ball I provided contains a patch, which changes this to "/usr". > > I have added your changes to my repo as vguitar_2.6-3 > Not sure, why you name it -3. Normally one bumps the Debian revision only if the the previous revision has

Re: gbp push fails

On 8/22/20 9:40 PM, Andrey Rahmatullin wrote: > On Sat, Aug 22, 2020 at 01:56:00PM +0200, Hilmar Preuße wrote: Hi, >>>> The person who did the upload for debian/0.7+git73896501cf-1 did not >>>> update the "upstream" branch, hence the tag was not cr

gbp push fails

Hi, I'm trying to do a "gbp push" for a repo and it fails: hille@sid:~/devel/proftp/aaa_git/proftpd-mod-case_master $ gbp push gbp:info: Pushing debian/0.7+git73896501cf-2 to origin gbp:info: Pushing upstream/0.7+git73896501cf to origin gbp:info: Pushing d8074c6b03512b4001b8e1ea06737afd989f139a

Re: gbp push fails

Am 22.08.2020 um 11:16 teilte Andrey Rahmatullin mit: > On Sat, Aug 22, 2020 at 01:08:52AM +0200, Hilmar Preuße wrote: Hi, >> One note: when I tried to do the push for the first time it told me >> there would be no "upstream/0.7+git73896501cf" tag, which was corre

Bug#970618: RFS: wwl/1.3+db-3 [QA] -- Calculates distance and azimuth between two Maidenhead locators

Am 20.09.2020 um 04:17 teilte Francisco Vilmar Cardoso Ruviaro mit: Hi, I am looking for a sponsor for my package "wwl": * Vcs : https://salsa.debian.org/debian/wwl Section : hamradio I was just curious and clicked on the Vcs link and noticed that it is invalid.

Built a Debian package using the source code of another one

Hi, the installation/compilation instructions for some proftp modules [1] say: "To install mod_proxy, go to the third-party module area in the proftpd source code and unpack the mod_proxy source tarball: $ cd proftpd-dir/contrib/ $ tar zxvf /path/to/mod_proxy-version.tar.gz after unpacking

Re: Built a Debian package using the source code of another one

Am 13.08.2020 um 16:38 teilte wf...@niif.hu mit: > Hilmar Preuße writes: Hi, >> the installation/compilation instructions for some proftp modules >> [1] say: >> "To install mod_proxy, go to the third-party module area in the >> proftpd source code and unp

Re: Adding a user in postinstall

Am 17.06.2020 um 11:55 teilte Markus mit: > While packaging a package for a Virtual Observatory server, I'm > encountering a postinst glitch in the CI that I don't quite > understand. > > This is about g...@salsa.debian.org:debian-astro-team/gavodachs.git, > the gavo branch. > > The idea is

Re: Overwriting files and not replacing packages - (no Replaces)

Am 12.11.2020 um 08:28 teilte Mathieu Malaterre mit: Hi, In this specific case I do not need 'Replaces:' (*), because 'libcharls.so' from libdcmtk-dev is not meant to be replaced by the one shipped in libcharls-dev (2.1.0+dfsg-7) (this is not the normal breaks+replaces pattern). Replaces

Package upload not processed?

Hi, the day before yesterday I uploaded the new version of a package. The email "Processing of proftpd-mod-proxy_0.7-1_source.changes" came in, nothing else: neither rejected nor accepted. Re-upload or still wait? Thanks! Hilmar -- sigfault OpenPGP_signature Description: OpenPGP digital

Re: Package upload not processed?

Am 03.11.2020 um 05:32 teilte Eriberto mit: Hi, I found these lines in logs inside mirror.ftp-master.debian.org: 20201031231816|process-upload|dak|proftpd-mod- proxy_0.7-1_source.changes|Error while loading changes file proftpd-mod-proxy_0.7-1_source.changes: No valid signature found. (GPG

Re: Conflicts does not remove old package

Am 08.01.2021 um 10:49 teilte Hilmar Preuße mit: Hi, When looking at the package texlive-base it already declares a Conflicts: (...) texlive-plain-generic (<< 2020.20200417). Hence I'd expect that old texlive-plain-generic is removed before the new texlive-base is installed. What

Conflicts does not remove old package

Hi, we got https://bugs.debian.org/978431 telling that the upgrade from buster to sid fails. This is also visible in piuparts [1]. Unpacking texlive-base (2020.20201203-2) over (2018.20190227-2) ... dpkg: error processing archive

Bug#979992: RFS: uwebsockets/18.19.0-1 [ITP] -- simple, secure & standards compliant web server

Control: merge -1 979990 Am 12.01.2021 um 17:44 teilte Aisha Tammy mit: Package: sponsorship-requests Severity: wishlist Dear mentors, -- sigfault OpenPGP_signature Description: OpenPGP digital signature

[d/watch] Need to modify name of upstream tar ball

Hi, short question for debian/watch. Our local version name of upstream tar ball is mmdd.tar.xz. In upstream the naming is -mm-dd.tar.xz . I've built a watch file, which correctly finds the new tar ball [1], but the comparison to version in Debian determines that the version in

Re: [d/watch] Need to modify name of upstream tar ball

Am 30.01.2021 um 04:21 teilte Eriberto Mota mit: Em sex., 29 de jan. de 2021 às 07:44, Hilmar Preuße escreveu: Hi, Unfortunately when looking at the tracker page [1], it tells "uscan had problems while searching for a new upstream version: In debian/watch no matching files for watch

Re: [d/watch] Need to modify name of upstream tar ball

Am 30.01.2021 um 17:28 teilte Mattia Rizzolo mit: On Sat, Jan 30, 2021 at 04:37:23PM +0100, Hilmar Preuße wrote: Hi, The part of the Debian udd database, which lists new upstream versions [1] prints that error message, hence there was a scan. BTW, that's also visible here: https

Re: [d/watch] Need to modify name of upstream tar ball

Am 28.01.2021 um 21:24 teilte Eriberto Mota mit: Hi Eriberto, My suggestion is always to use "releases" instead of "tags". Also, you should use uversionmangle instead of filenamemangle. version=4 opts=uversionmangle=s/-//g \ https://github.com/TeXworks/manual/releases archive/(\d\S+)\.tar\.gz

Debian/watch file does not ignore beta version

Hi, this is the current debian/watch file for proftp, it is not in the archive yet, just on salsa: version=4 opts=repack,compression=gz,repacksuffix=+dfsg,dversionmangle=s/\+dfsg//,\ uversionmangle=s/(\d)[_\.\-\+]?((RC|rc|pre|dev|beta|alpha)\d*)$/$1~$2/,\

Re: pgpsigurlmangle in debian/watch

Am 15.03.2021 um 00:16 teilte Hilmar Preuße mit: Hi, uscan -ddd tries to download from https://github.com/proftpd/proftpd/releases/download/v/proftpd-v1.3.7a.tar.gz.asc How to I refer to upstreams new version in pgpsigurlmangle ? Finally it was more easy that I thought, solution is in [1

Re: pgpsigurlmangle in debian/watch

Am 15.03.2021 um 08:39 teilte Geert Stappers mit: On Mon, Mar 15, 2021 at 12:16:24AM +0100, Hilmar Preuße wrote: Hi, My attempt to implement signature check is pgpsigurlmangle=s@archive@releases/download/v$1@;\ s/([^\/]+)\.tar\.gz/proftpd-$1\.tar\.gz/;\ s/$/.asc/ \ uscan -ddd tries

pgpsigurlmangle in debian/watch

Hi, this is rather a question regarding handling d/watch in general. Upstream source is https://github.com/proftpd/proftpd/archive/v1.3.7.tar.gz PGPG sig is https://github.com/proftpd/proftpd/releases/download/v1.3.7/proftpd-1.3.7.tar.gz.asc My attempt to implement signature check is

Contributors in d/copyright

Hi, dumb question. I convert another d/copyright into DEP5 format. The old file contains: Upstream author: Werner Lemberg With help from: Per BOTHNER Noah FRIEDMAN Kenichi HANDA Gernot HASSENPFLUG Wonkoo KIM Yi-Liang KUO Hin-Tak LEUNG Eberhard MATTES

TeXworks: embedded-library usr/bin/texworks: pcre3

Hi all, 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. Doing a "grep -ri pcre" in the build tree does now show

Re: TeXworks: embedded-library usr/bin/texworks: pcre3

Am 12.04.2021 um 23:12 teilte Andrey Rahmatullin mit: On Mon, Apr 12, 2021 at 10:42:47PM +0200, Hilmar Preuße wrote: Hi, 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

Re: Failed build for seqan2 on i386

Am 12.02.2021 um 11:01 teilte Andreas Tille mit: On Fri, Feb 12, 2021 at 02:39:25PM +0500, Andrey Rahmatullin wrote: Hi, 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

Re: Help With debian/rules File Without Build Tool

Am 30.08.2021 um 13:22 teilte debian-ment...@jugra.de mit: Hi, maybe you can try to copy with cat <<'EOF' >>debian/$PACKAGENAME.install program usr/bin EOF ...and replace the override_dh_auto_clean: rm -f program By a file debian/clean containing the names of the be deleted files. H.

Re: Debian/watch file does not ignore beta version

On 6/25/21 3:32 AM, Paul Wise wrote: On Thu, Jun 24, 2021 at 10:01 PM Hilmar Preuße wrote: Hi, Sorry for late Reply! uversionmangle=s/(\d)[_\.\-\+]?((RC|rc|pre|dev|beta|alpha)\d*)$/$1~$2/,\ ... According to [1] the entry "uversionmangle=..." should handle the case that there cou

Re: RFS: looking for a sponsor to upgrade mg (repost)

Am 22.09.2021 um 12:42 teilte Harald Dunkel mit: Hi, I am looking for a sponsor to review the new mg package for Sid, as it can be found on https://salsa.debian.org/debian/mg . Its not tagged yet. (I missed the RFS in the subject line, so this is a repost.) Please refer to the mentors FAQ:

Re: Packaging help: users and directories

Am 29.12.2021 um 12:36 teilte Gavin Henry mit: Hi, What's this for, when it looks like this was written manually? Google shows nothing: https://salsa.debian.org/dns-team/bind9/-/blob/debian/main/debian/bind9.postinst#L35 #DEBHELPER# One of the first google hits:

Bug#1005371: marked as done (RFS: libfilezilla/0.36.0-2 -- build high-performing platform-independent programs (runtime lib))

Am 13.02.2022 um 13:11 teilte Philip Wyett mit: Hi, Sorry if my note has confused. Imported into salsa, but still needs the source only upload as I am not a DM and still need others to upload. MAybe an appropriate time for me to go for DM? DM's can have uploads permits for specific packages,

Re: Do autopkgtest for non-listed architectures prevent migration?

Am 22.01.2022 um 15:06 teilte Markus Blatt mit: Hi, I limit the architecture to only 64bit architectures by having "Architecture: amd64 arm64 ia64 mips64el ppc64el" in d/control. Yet this does not seem to respected for autopkgtest as it still tries to run the test for i386 and armhf. The

Re: Bug#1004024: RFS: fig2sxd/0.23-2 -- convert XFig files to OpenOffice.org format

Am 19.01.2022 um 21:40 teilte Alexander Bürger mit: Hi, Unfortunately, the first attempt to use debhelper in debian/rules failed to build and I only noticed that after publication on gitlab with debian/changelog specifying version 0.23-1. The packaging fix did, of course, not change anything

Bug#1004024: RFS: fig2sxd/0.23-2 -- convert XFig files to OpenOffice.org format

Am 20.01.2022 um 08:49 teilte Alexander Bürger mit: Hi, I do not see any solution to this problem: - rewriting the commit history on gitlab is not an option Why not? You just have to remove the tag and rewrite the commit message. Then fix the debian/changelog and try again. -

Deleting accepted upload?

Hi all, yesterday I uploaded dvisvgm_2.13-1 to the archive. For any unknown reason I deleted the changelog entry for version 2.12-4 from the d/changelog file, this version is currently in testing. I tried to cancel the upload using dcut, but this does not work. How to proceed? - Can we

Re: Deleting accepted upload?

Am 24.01.2022 um 09:43 teilte Andrey Rahmatullin mit: On Mon, Jan 24, 2022 at 09:14:08AM +0100, Hilmar Preuße wrote: Hi Andrey, - Can we remove that version 2.13-1 from unstable? We shouldn't. And we can't remove it from user machines. Yes, correct. - Should I simply upload 2.13-2

Upload for Debian QA

Hi all, TeXinfo 7.1 does not migrate to testing b/c the test suite of autoproject returns with exit code > 0. I've filed a bug report and created a patch for the issue. The package is maintained by the Debian QA group. What else can be done from my side? Hilmar -- Testmail

Access to porter boxes?

Hi, I have the need to access a porter box, in this situation zelenka.debian.org. The DSA page [1] says DM's (like me) would need to apply through the NEW members site. I went to [2] and logged in using my salsa account, selected "Site wizard" and "Request guest account". The resulting page

Disabling ccache in Salsa CI Jobs?

Hi, Recently I pushed a new version of proftp to salsa. The configured salsa CI Jobs [1] now fail [2]. The relevant error message is in the job log [3]: gcc -Wdate-time -D_FORTIFY_SOURCE=2 -DHAVE_CONFIG_H -DLINUX -I. -I../.. -I../../include -I./../../include -I/usr/include/mariadb/mysql

Re: Debian versioning question

On 10/13/23 01:32, Mattia Rizzolo wrote: On Thu, Oct 12, 2023 at 11:52:30PM +0200, Preuße, Hilmar wrote: Hi Mattia, The upstream minor versions are always determined by letters, so I'm unsure how to make clear that 1.3.8a+ is later than 1.3.8+. Any hints? This is a real sad interaction

Re: Specifying "Build Type: all" using sbuild

Am 01.06.2022 um 13:45 teilte Andrey Rahmatullin mit: On Wed, Jun 01, 2022 at 01:43:12PM +0200, Hilmar Preuße wrote: Moin, Do you mean "Build Architecture" instead? No. Have a look at the links I posted: I did that before asking. I'm pretty sure you did! Therefore I'm

Re: Specifying "Build Type: all" using sbuild

Am 01.06.2022 um 13:38 teilte Andrey Rahmatullin mit: On Wed, Jun 01, 2022 at 01:20:34PM +0200, Hilmar Preuße wrote: Hi, I had a look at the manual page. The build log (see both links) makes a difference between "Arch type" and "Build type". Does it? Do you mean

Specifying "Build Type: all" using sbuild

Hi, When using "Build Type: any" for a source package the package build runs fine, it fails for "Build Type: all". Before upload I tested the build using "sbuild --no-run-lintian texlive-bin_2022.20220321.62855-3.dsc -d unstable-amd64-sbuild" and it worked fine. How do I specify "Build

Re: Specifying "Build Type: all" using sbuild

Am 01.06.2022 um 13:16 teilte Arnaud Ferraris mit: Hi, You can use the "--arch-all --no-arch-any" combination of options (--no-arch-any being the important part). Generally speaking, sbuild provides a lot of useful options, I encourage you to read its man page so you get an idea of what's

Re: Specifying "Build Type: all" using sbuild

Am 01.06.2022 um 13:16 teilte Arnaud Ferraris mit: Hi Arnaud, hi Andrey, You can use the "--arch-all --no-arch-any" combination of options (--no-arch-any being the important part). Generally speaking, sbuild provides a lot of useful options, I encourage you to read its man page so you get an

Bug#1012319: RFS: texlive-bin/2022.20220321.62855-4 [RC] -- TeX Live: LuaJIT, modified for use with LuaJITTeX (development part)

Am 04.06.2022 um 09:36 teilte Hilmar Preuße mit: Am 04.06.2022 um 00:24 teilte Hilmar Preuße mit: Dear mentors, I've uploaded a new improved version of texlive-bin/2022.20220321.62855-4, dget link is on mentors, please be so kind to upload to the archive. https://mentors.debian.net/debian

Bug#1012196: buglist

Am 07.06.2022 um 18:32 teilte André Flechs mit: I added all issues to changelog as Closes. How can I remove the tag? https://www.debian.org/Bugs/server-control Hilmar -- sigfault OpenPGP_signature Description: OpenPGP digital signature

Bug#1012319: RFS: texlive-bin/2022.20220321.62855-4 [RC] -- TeX Live: LuaJIT, modified for use with LuaJITTeX (development part)

Package: sponsorship-requests Severity: important Dear mentors, My GPG key has expired, hence I need a sponsor for this upload. I am looking for a sponsor for my package "texlive-bin": * Package name: texlive-bin Version : 2022.20220321.62855-4 Upstream Author : [fill in

Bug#1012319: RFS: texlive-bin/2022.20220321.62855-4 [RC] -- TeX Live: LuaJIT, modified for use with LuaJITTeX (development part)

Am 04.06.2022 um 00:24 teilte Hilmar Preuße mit: Dear mentors, Package: sponsorship-requests Severity: important Dear mentors, My GPG key has expired, hence I need a sponsor for this upload. Please put the request on hold, I'll (eventually) prepare a new upload. Hilmar -- sigfault

Re: Disabling ccache in Salsa CI Jobs?

Am 27.04.2022 um 13:00 teilte Michael Tokarev mit: Hi Michael, Many thanks for your E-mail. As far as I can see, ccache failing like this is because you run compilation jobs in the install or binary target, not in build target. These are run as different users. I don't know if this is

Bug#1020929: RFS: tex-gyre/20180621-4 -- scalable PostScript and OpenType fonts based on URW Fonts

Am 28.09.2022 um 22:47 teilte Bastian Germann mit: Hi Bastian, Is this a team upload? If so, please add an entry to the changelog. I've added "* Team upload." to the top of the changelog. Now lintian complains: unnecessary-team-upload The debian/changelog file refers to a "Team upload"

  1   2   >