Rebuilding Debian packages
Hello If the dependency graph of a binary package in the unstable distribution is changed (e.g. because of the 64-bit time_t transition) shall the binary package be rebuilt in the distribution? - Tommi -- Kotisivu / Homepage: http://www.iki.fi/tohoyn/ Sähköposti / E-Mail: tommi.hoynalan...@iki.fi GPG-sormenjälki / GPG fingerprint: 55F4 2477 7155 3528 5CB2 2B7A BB86 1FDE 4046 0F83 FM, Debian-ylläpitäjä / M.Sc., Debian Maintainer
FWD: Copyright in LGPL projects
Sent message incorrectly to debian-mentors-request instead of debian-mentors. Correcting. Forwarded Message Subject: Copyright in LGPL projects Date: Mon, 4 Mar 2024 11:10:58 +0530 From: Alan M Varghese To: 1065...@bugs.debian.org CC: Matthias Geiger , SmartList Hello Mentors, I have been working on packaging Hyprland window manager. hyprlang[0] (with a 'g') is a new dependency for this project. This project (hyprlang) is licensed under LGPL. But, the project authors haven't included a copyright notice anywhere in the project. It turns out that the authors are not sure if this is required for an LGPL project[1]. From a Debian perspective, what is the recommendation regarding this? Do we require projects to include the copyright information along with LGPL? If the copyright *has* to be included, is it enough to include it in a COPYRIGHT file? I couldn't find an example of a project that does this. Most projects seem to include a copyright line along with a short form of LGPL in each file. (I think it may be more appealing to upstream authors if we don't have to include the copyright in every file). For example, libplacebo[2] is a library I found installed on my system that uses LGPL. This project does not have a common copyright file, but there are copyright notices in some source files[3]. While some other source files in this project do not have a copyright notice[4][5][6]. Note: my doubts are specifically regarding the LGPL license. For other licenses like BSD, I see both practices of including a COPYRIGHT file as well as a short copyright notice in each file, or a combination of the two. Thanks, Alan M Varghese [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065352 [1] https://github.com/hyprwm/hyprlang/issues/28 [2] https://code.videolan.org/videolan/libplacebo [3] https://code.videolan.org/videolan/libplacebo/-/blob/master/src/dither.c?ref_type=heads [4] https://code.videolan.org/videolan/libplacebo/-/blob/master/src/dummy.c?ref_type=heads [5] https://code.videolan.org/videolan/libplacebo/-/blob/master/src/cache.c?ref_type=heads [6] https://code.videolan.org/videolan/libplacebo/-/blob/master/src/colorspace.c?ref_type=heads
Bug#1065389: RFS: python-click/8.1.7-1 [ITA] -- Wrapper around optparse for command line utilities - documentation
Hi! On Mon, Mar 4, 2024 at 1:51 AM Akash Doppalapudi wrote: > > Package: sponsorship-requests > Severity: normal > > Dear mentors, > > I am looking for a sponsor for my package "python-click": > > * Package name : python-click > Version : 8.1.7-1 > Upstream contact : cont...@palletsprojects.com > * URL : https://github.com/pallets/click > * License : BSD-3-clause > * Vcs : > https://salsa.debian.org/python-team/packages/python-click > Section : python > > The source builds the following binary packages: > >python3-click - Wrapper around optparse for command line utilities - > Python 3.x >python-click-doc - Wrapper around optparse for command line utilities > - documentation > > To access further information about this package, please visit the > following URL: > >https://mentors.debian.net/package/python-click/ > > Alternatively, you can download the package with 'dget' using this command: > >dget -x > https://mentors.debian.net/debian/pool/main/p/python-click/python-click_8.1.7-1.dsc > > Changes since the last upload: > > python-click (8.1.7-1) unstable; urgency=medium > . > * New upstream version 8.1.7 > * New Maintainer (Closes: #1065251) I would like to suggest you contact Peter Pentchev as he/she has reported ITA earlier than your ITA. And would you really want to maintain these packages without Debian Python Team? No other meaning, just considering these packages should be maintained under DPT sounds more reasonable. BR, Bo > * d/control: > - Change Maintainer name > - Add python-click-doc in Suggests for python3-click > * d/copyright: > - Add new maintainer name in copyright stanza > > Regards, > -- >Akash Doppalapudi
Re: Remove package from unstable?
On Mon, Mar 04, 2024 at 12:09:26AM +0100, Hilmar Preuße wrote: > On 29.02.24 00:42, Lyndon Brown wrote: > > Hello, > > > b) Re-upload 2.10.08+ds-1 with a version number like '2.11.01+ds-3- > > really2.10.08+ds-1', such that it will count as a higher version number > > than the mistaken upload of 2.11.01+ds-3 and thus replace it in package > > upgrades. You'd then continue with this pattern for 2.10.x updates > > until the eventual proper migration of 2.11 to unstable, at which point > > you can simplify the version numbering back to '2'11.x'. > > > > I'm sure you'll agree that option B would probably be preferable. > > > > Yes, agreed. Currently I'm trying to find out how to reflect that downgrade > in my gbp style git repository. > > I try to build my source package by calling "gbp buildpackage > --git-upstream-tree=upstream_2.10.08+ds", where "upstream_2.10.08+ds" is a > new upstream branch containing the source code for version 2.10.08. It tries > to build the binary package, which fails b/c the BD's are not fulfilled. > However I just need the source package. How I can prevent from running > "dpkg-buildpackage -us -uc -ui -i -I", I just need "dpkg-buildpackage > -S". Have you just tried passing through -S from gbp? As in "gbp buildpackage -S"? It might not work if you have set a different builder like schroot, but you can just pass --git-builder=debuild or similar in that case. > > Hilmar > -- > Testmail > -- Loren M. Lang lor...@north-winds.org http://www.north-winds.org/ Public Key: http://www.north-winds.org/lorenl_pubkey.asc Fingerprint: 7896 E099 9FC7 9F6C E0ED E103 222D F356 A57A 98FA signature.asc Description: PGP signature
Re: Remove package from unstable?
On 29.02.24 00:42, Lyndon Brown wrote: Hello, b) Re-upload 2.10.08+ds-1 with a version number like '2.11.01+ds-3- really2.10.08+ds-1', such that it will count as a higher version number than the mistaken upload of 2.11.01+ds-3 and thus replace it in package upgrades. You'd then continue with this pattern for 2.10.x updates until the eventual proper migration of 2.11 to unstable, at which point you can simplify the version numbering back to '2'11.x'. I'm sure you'll agree that option B would probably be preferable. Yes, agreed. Currently I'm trying to find out how to reflect that downgrade in my gbp style git repository. I try to build my source package by calling "gbp buildpackage --git-upstream-tree=upstream_2.10.08+ds", where "upstream_2.10.08+ds" is a new upstream branch containing the source code for version 2.10.08. It tries to build the binary package, which fails b/c the BD's are not fulfilled. However I just need the source package. How I can prevent from running "dpkg-buildpackage -us -uc -ui -i -I", I just need "dpkg-buildpackage -S". Hilmar -- Testmail OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1065397: RFS: libunistring/1.2-1 -- Unicode string library for C
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "libunistring": * Package name : libunistring Version : 1.2-1 Upstream contact : Bruno Haible * URL : https://www.gnu.org/software/libunistring/ * License : GPL-2+ with distribution exception, Expat and GPL-2+, LGPL-3+ or GPL-2+, FreeSoftware, GPL-3+, GPL-3+ or GFDL-NIV-1.2+, X11, GPL-2+ with distribution exception, GPL-2+ * Vcs : https://git.jff.email/cgit/libunistring.git Section : libs The source builds the following binary packages: libunistring-dev - Unicode string library for C - development files libunistring5 - Unicode string library for C To access further information about this package, please visit the following URL: https://mentors.debian.net/package/libunistring/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/libu/libunistring/libunistring_1.2-1.dsc or from git https://git.jff.email/cgit/libunistring.git/?h=release%2Fdebian%2F1.2-1 Changes since the last upload: libunistring (1.2-1) unstable; urgency=medium . * New upstrem release. - Refresh / Rebuild symbols file. * debian/copyright: - Add 2024 to myself. - Refresh uploader copyright years. * Remove unused patches: - debian/patches/0100-float-endian-detection.patch. CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Jörg Frings-Fürst D-54470 Lieser git: https://git.jff.email/cgit/ Skype:jff-skype@jff.email Jami: joergfringsfuerst Telegram: @joergfringsfuerst Matrix: @joergff:matrix.snct-gmbh.de My wish list: - Please send me a picture from the nature at your home. signature.asc Description: This is a digitally signed message part
Re: Bug#1065078: Question about the debian group on Salsa
On Sun, Mar 03, 2024 at 12:02:36AM -0700, Soren Stoutner wrote: > Loren, > > Yes, I would say that is generally correct. If you have a package that is > team maintained, it is best under the team namespace. If it is not team > maintained, it is generally best under the debian namespace (which is the > team > of all Debian Developers). It makes it easier for others to pick up if > something happens to you. > > However, there may be specific cases where you do want to keep it in your own > namespace. I maintain one package where I am also the upstream developer. I > keep the Debian packaging in my own namespace because I want to have a very > high threshold for other people making changes to it. At this stage, if > something were to happen to me, both the Debian package and the upstream > project would need to be adopted by someone else, which would probably > necessitate a renaming of the project. Down the road, I would like to get > more people involved in both the upstream development and the Debian > packaging. When that happens I will probably move the Salsa project to a > team > namespace. > > There is certainly nothing wrong with keeping your project under your own > namespace, but if you would like to move it to the debian namespace, grant me > full access to it (my Salsa username is soren) and I can then move it to the > debian namespace and grant you full access to the project there. Thanks! I've granted you full access to https://salsa.debian.org/penguin359/tiv -Loren > > Soren > > On Saturday, March 2, 2024 11:34:14 PM MST Loren M. Lang wrote: > > On Sat, Mar 02, 2024 at 01:11:46AM +0100, Salvo Tomaselli wrote: > > > In data venerdì 1 marzo 2024 05:12:51 CET, Soren Stoutner ha scritto: > > > > Generally you should create the repository under the debian namespace > > > > > > You need to ask a DD to do that. Non DD don't have permissions for this. > > > > So is having all packages (at least those not maintained by a team) > > under the debian/ namespace considered a best practice for all but the > > most sensitive of packages? Should I actually have my own package > > transfered to this namespace? > > > > I just have a small, CLI package that I maintain alone and, since I > > don't have DD permissions, just assumed that I should put it under my > > own namespace. Is it recommended to just keep it under the neutral > > debian namespace just in case I am no longer able to keep it maintained > > in the future? > > > > My current package is https://salsa.debian.org/penguin359/tiv > > > > -Loren > > -- > Soren Stoutner > so...@debian.org -- Loren M. Lang lor...@north-winds.org http://www.north-winds.org/ Public Key: http://www.north-winds.org/lorenl_pubkey.asc Fingerprint: 7896 E099 9FC7 9F6C E0ED E103 222D F356 A57A 98FA signature.asc Description: PGP signature
Bug#1065389: RFS: python-click/8.1.7-1 [ITA] -- Wrapper around optparse for command line utilities - documentation
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "python-click": * Package name : python-click Version : 8.1.7-1 Upstream contact : cont...@palletsprojects.com * URL : https://github.com/pallets/click * License : BSD-3-clause * Vcs : https://salsa.debian.org/python-team/packages/python-click Section : python The source builds the following binary packages: python3-click - Wrapper around optparse for command line utilities - Python 3.x python-click-doc - Wrapper around optparse for command line utilities - documentation To access further information about this package, please visit the following URL: https://mentors.debian.net/package/python-click/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/p/python-click/python-click_8.1.7-1.dsc Changes since the last upload: python-click (8.1.7-1) unstable; urgency=medium . * New upstream version 8.1.7 * New Maintainer (Closes: #1065251) * d/control: - Change Maintainer name - Add python-click-doc in Suggests for python3-click * d/copyright: - Add new maintainer name in copyright stanza Regards, -- Akash Doppalapudi OpenPGP_0xBCBCAE31ECE05007.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1065384: RFS: psocksxx/1.1.1-4 -- psocksxx is a C++ wrapper for POSIX sockets (documentation)
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "psocksxx": * Package name : psocksxx Version : 1.1.1-4 Upstream contact : [fill in name and email of upstream] * URL : https://nukedzn.github.io/psocksxx * License : LGPL-3+ * Vcs : https://git.jff.email/cgit/psocksxx.git Section : libs The source builds the following binary packages: libpsocksxx0t64 - psocksxx is a C++ wrapper for POSIX sockets libpsocksxx-dev - psocksxx is a C++ wrapper for POSIX sockets (development files) libpsocksxx-doc - psocksxx is a C++ wrapper for POSIX sockets (documentation) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/psocksxx/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/p/psocksxx/psocksxx_1.1.1-4.dsc or from git https://git.jff.email/cgit/psocksxx.git/?h=release%2Fdebian%2F1.1.1-4 Changes since the last upload: psocksxx (1.1.1-4) unstable; urgency=medium . * debian/control: - Change to new repository URL. * Declare compliance with Debian Policy 4.6.2.0 (No changes needed). * debian/changelog: - Add 2024 to myself. CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Jörg Frings-Fürst D-54470 Lieser git: https://git.jff.email/cgit/ Skype:jff-skype@jff.email Jami: joergfringsfuerst Telegram: @joergfringsfuerst Matrix: @joergff:matrix.snct-gmbh.de My wish list: - Please send me a picture from the nature at your home. signature.asc Description: This is a digitally signed message part
Bug#1065374: RFS: sane-backends/1.3.0-1 -- API development library for scanners
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "sane-backends": * Package name : sane-backends Version : 1.3.0-1 Upstream contact : * URL : http://www.sane-project.org * License : Artistic, GPL-2, GPL-3+, GPL-2+ with sane exception, LGPL-2.1+, GPL-2+ * Vcs : https://git.jff.email/cgit/sane-backends.git Section : graphics The source builds the following binary packages: sane-utils - API library for scanners -- utilities libsane-common - API library for scanners -- documentation and support files libsane1 - API library for scanners libsane-dev - API development library for scanners [development files] To access further information about this package, please visit the following URL: https://mentors.debian.net/package/sane-backends/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/s/sane-backends/sane-backends_1.3.0-1.dsc or from git https://git.jff.email/cgit/sane-backends.git?h=release%2Fdebian%2F1.3.0-1 Changes since the last upload: sane-backends (1.3.0-1) unstable; urgency=medium . * New upstream release. - debian/sane-utils.install: Install new saned.install.md. - Refresh patches. * debian/control: - Replace obsolete pkg-config with pkgconf. * New debian/patches/0610-fix_groff_font_warnings.patch: - Fix missing font messages. * Install saned.service mask symlink into /usr (Closes: #1059186). - Thanks to Chris Hofstaedtler . * debian/copyright: - Add 2024 to myself. - New po/zh_CN.po. CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Jörg Frings-Fürst D-54470 Lieser git: https://git.jff.email/cgit/ Skype:jff-skype@jff.email Jami: joergfringsfuerst Telegram: @joergfringsfuerst Matrix: @joergff:matrix.snct-gmbh.de My wish list: - Please send me a picture from the nature at your home. signature.asc Description: This is a digitally signed message part
Bug#1065372: RFS: hexwalk/1.7.1-2 [ITP] -- HexWalk is an Hex analyzer, editor and viewer
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "hexwalk": * Package name : hexwalk Version : 1.7.1-2 Upstream contact : project> * URL : https://www.hexwalk.com * License : GPL-3.0+ * Vcs : https://github.com/gcarmix/hexwalk Section : editors The source builds the following binary packages: hexwalk - HexWalk is an Hex analyzer, editor and viewer To access further information about this package, please visit the following URL: https://mentors.debian.net/package/hexwalk/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/h/hexwalk/hexwalk_1.7.1-2.dsc Changes for the initial release: hexwalk (1.7.1-2) stable; urgency=medium
Bug#1064934: RFS: nanomsg/1.2.1+dfsg-1 -- nanomsg utilities
Hello, +++ nanomsg-1.2.1+dfsg/src/utils/chunkref.c 2024-02-03 23:45:24.0 +0100 @@ -1,5 +1,6 @@ /* Copyright (c) 2013 Martin Sustrik All rights reserved. +Copyright 2024 Staysail Systems, Inc. Anyway, I didn't sponsor, but gave you DM for the package. Feel free to add the missing copyright holder and upload. G. On Tue, 27 Feb 2024 21:09:16 + Phil Wyett wrote: Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "nanomsg": * Package name : nanomsg Version : 1.2.1+dfsg-1 Upstream contact : Martin Sústrik * URL : https://nanomsg.org/ * License : Expat * Vcs : https://salsa.debian.org/debian/nanomsg Section : libs The source builds the following binary packages: libnanomsg6 - high-performance implementation of scalability libraries libnanomsg-dev - nanomsg development files nanomsg-utils - nanomsg utilities To access further information about this package, please visit the following URL: https://mentors.debian.net/package/nanomsg/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/n/nanomsg/nanomsg_1.2.1+dfsg-1.dsc Changes since the last upload: nanomsg (1.2.1+dfsg-1) experimental; urgency=medium . * New upstream version 1.2.1. * Remove not required patches. * Remove not required lintian overrides. * 'd/libnanomsg6.symbols': Correct typographical error. Note: Could I be given upload rights to this package when accepted please. Regards Phil -- Playing the game for the games sake. Web: * Debian Wiki: https://wiki.debian.org/PhilWyett * Website: https://kathenas.org * Social Debian: https://pleroma.debian.social/kathenas/ * Social Instagram: https://www.instagram.com/kathenasorg/ OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1065194: RFS: python-raccoon/3.1.1-1 -- Python DataFrame with fast insert and appends (Python 3)
Hi, I've linked that bug in changelog in the 2nd upload of the package in mentors. Thanks On March 3, 2024 12:54:58 PM GMT+05:30, Bo YU wrote: >Hi, >On Fri, Mar 01, 2024 at 11:54:26PM +0530, Akash Doppalapudi wrote: >> Package: sponsorship-requests >> Severity: normal >> >> Dear mentors, >> >> I am looking for a sponsor for my package "python-raccoon": >> >> * Package name : python-raccoon >> Version : 3.1.1-1 >> Upstream contact : Ryan Sheftel >> * URL : https://github.com/rsheftel/raccoon >> * License : MIT >> * Vcs : https://salsa.debian.org/debian/python-raccoon >> Section : python >> >> The source builds the following binary packages: >> >> python3-raccoon - Python DataFrame with fast insert and appends (Python 3) >> >> To access further information about this package, please visit the following >> URL: >> >> https://mentors.debian.net/package/python-raccoon/ >> >> Alternatively, you can download the package with 'dget' using this command: >> >> dget -x >> https://mentors.debian.net/debian/pool/main/p/python-raccoon/python-raccoon_3.1.1-1.dsc >> >> Changes since the last upload: >> >> python-raccoon (3.1.1-1) unstable; urgency=medium >> . >> * New upstream version 3.1.1 >> * New Maintainer > >I think you need close this issue also: >https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052685 > >BR, >Bo
