Bug#1021430: RFS: wine/7.0~repack-8~bpo11+1 -- Windows API implementation - standard suite
Control: retitle -1 RFS: wine/7.0~repack-10~bpo11+1 -- Windows API implementation - standard suite thanks Dear mentors, I am looking for a sponsor for my package "wine". It is (now) a trivial backport (dch --bpo) but it does need to go through NEW: * Package name : wine Version : 7.0~repack-10~bpo11+1 * Vcs : https://salsa.debian.org/wine-team/wine Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/w/wine/wine_7.0~repack-10~bpo11+1.dsc I'll also try and remember to use rebases rather than merges for the wine repo now (the backports branch has been force updated to match). signature.asc Description: PGP signature
Bug#1021638: RFS: gamehub/0.16.3-2-master+ds-1~bpo11+1 -- Unified library for games from multiple sources
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "gamehub". It is a trivial backport (dch --bpo) but it does need to go through NEW: * Package name : gamehub Version : 0.16.3-2-master+ds-1~bpo11+1 Upstream contact : Anatoliy Kashkin * URL : https://tkashkin.github.io/projects/gamehub/ * License : CC0-1.0, GPL-3+ * Vcs : https://salsa.debian.org/yangfl-guest/gamehub Section : games The source builds the following binary packages: gamehub - Unified library for games from multiple sources To access further information about this package, please visit the following URL: https://mentors.debian.net/package/gamehub/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/g/gamehub/gamehub_0.16.3-2-master+ds-1~bpo11+1.dsc Changes since the last upload: gamehub (0.16.3-2-master+ds-1~bpo11+1) bullseye-backports; urgency=medium . * Rebuild for bullseye-backports. . gamehub (0.16.3-2-master+ds-1) unstable; urgency=medium . * New upstream release * Fix FTBFS (Closes: #1011700) * Bump Standards-Version to 4.6.1 . gamehub (0.16.1-2-master+ds-1) unstable; urgency=medium . * New upstream release * Bump Standards-Version to 4.6.0 . gamehub (0.16.0-1-master+ds-1) unstable; urgency=medium . * Initial release (Closes: #982335) Regards, -- Phil Morrell signature.asc Description: PGP signature
Bug#1021636: RFS: lexicon/3.9.4-1~bpo11+1 [Team] -- CLI for manipulating DNS records on various DNS providers (Python 3)
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "lexicon". It is a trivial backport (dch --bpo) but it does need to go through NEW: * Package name : lexicon Version : 3.9.4-1~bpo11+1 * URL : https://github.com/AnalogJ/lexicon * License : MIT/Expat * Vcs : https://salsa.debian.org/python-team/packages/python-lexicon Section : python The source builds the following binary packages: python3-lexicon - Manipulate DNS records on various DNS providers (Python 3) lexicon - CLI for manipulating DNS records on various DNS providers (Python 3) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/lexicon/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/l/lexicon/lexicon_3.9.4-1~bpo11+1.dsc Changes since the last upload: lexicon (3.9.4-1~bpo11+1) bullseye-backports; urgency=medium . * Rebuild for bullseye-backports. . lexicon (3.9.4-1) unstable; urgency=medium . * Team upload. . [ Ondřej Nový ] * d/control: Update Vcs-* fields with new Debian Python Team Salsa layout. . [ Sandro Tosi ] * Use the new Debian Python Team contact name and address . [ Ana Custura ] * New upstream version 3.3.17 . [ Harlan Lieberman-Berg ] * New upstream version 3.9.4 (Closes: #1005686) * Update dependencies in d/control * Bump S-V, dh * Update tests run. * Add Rules-Requires-Root * Switch to pyproject plugin for pybuild * Add lintian override for very long lines in test dir Regards, -- Phil Morrell signature.asc Description: PGP signature
Bug#1021627: RFS: widelands/2:1.0-4~bpo11+1 [Team] -- fantasy real-time strategy game
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "widelands". It is a trivial backport (dch --bpo) but it does need to go through NEW: * Package name : widelands Version : 2:1.0-4~bpo11+1 * URL : http://www.widelands.org/ * License : Eris, GPL-2+, CC-BY-SA-3.0, Apache2.0, GPL-2, SIL-Open-Font-License * Vcs : https://salsa.debian.org/games-team/widelands Section : games The source builds the following binary packages: widelands - fantasy real-time strategy game widelands-data - fantasy real-time strategy game (data files) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/widelands/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/w/widelands/widelands_1.0-4~bpo11+1.dsc Changes since the last upload: widelands (2:1.0-4~bpo11+1) bullseye-backports; urgency=medium . * Rebuild for bullseye-backports. . widelands (2:1.0-4) unstable; urgency=medium . * Team upload. * Source only upload. . widelands (2:1.0-3) unstable; urgency=medium . * Team upload. * Properly transit previously shipped font to symlink of packaged font. (Closes: #1018966) . widelands (2:1.0-2) unstable; urgency=medium . * Team upload. * Source-only no-change upload to enable migration to testing. . widelands (2:1.0-1) unstable; urgency=medium . * New upstream release: The 1.0 Release!! - Some highlights from the hundreds of changes: - A new tribe: the Amazons - An add-on system - A third frisians scenario - Dynamic tribe loading to speed up game loading - Targeting individual map objects for removal - Mute/unmute messages by buildings - Fully redesigned main menu - Configurable keyboard shortcuts - Enhanced keyboard and mousewheel support in the UI - Long-term stable Lua API for game content designers - Closes: #992626 * Update the packaging for this new version - Bump the epoch to 2. Version 1:21 was corresponding to build21 upstream, but now upstream version is 1.0, so bumping the epoch is unavoidable. - Update d/watch for this new numbering schema (Closes: #1005370) - Add a build-dep on libcurl4-gnutls-dev. - Refresh patches. * Fix lintian overrides * Add a patch to fix some spelling issues reported by Lintian . widelands (1:21-2) unstable; urgency=medium . [ Stephen Kitt ] * Remove Enrico Tassi from uploaders. Closes: #995561. . [ Martin Quinson ] * d/p/gcc-12: Fix FTBFS with gcc-12. Closes: #1013066. * Don't depend on fonts-lklug-sinhala as this font is not used anymore. * Depend on culmus-fancy to get TaameyFrankCLM fonts. - Bump Standards-Version to 4.6.1 -- no changes needed. Regards, -- Phil Morrell signature.asc Description: PGP signature
Bug#1021430: RFS: wine/7.0~repack-8~bpo11+1 -- Windows API implementation - standard suite
Control: reopen -1 Control: retitle -1 RFS: wine/7.0~repack-9~bpo11+1 -- Windows API implementation - standard suite thanks wine (7.0~repack-9~bpo11+1) bullseye-backports; urgency=medium . * Rebuild for bullseye-backports. * depend on libxml-libxml-perl. Thanks to Adam Borowski * add myself to Uploaders On Sat, Oct 08, 2022 at 08:57:11PM +0200, Adam Borowski wrote: > On Sat, Oct 08, 2022 at 01:54:40PM +0100, Phil Morrell wrote: > > wine (7.0~repack-8~bpo11+1) bullseye-backports; urgency=medium > > . > >* Rebuild for bullseye-backports. > >* drop adapter_vk.c change from vulkan.patch > >* require libvulkan-dev newer than bullseye > >* add myself to Uploaders > >* omit dpkg (>= 1.21.0) constraint > > cd dlls/opengl32 && ./make_opengl > Can't locate XML/LibXML.pm in @INC (you may need to install the XML::LibXML > module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.32.1 > /usr/local/share/perl/5.32.1 /usr/lib/x86_64-linux-gnu/perl5/5.32 > /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base > /usr/lib/x86_64-linux-gnu/perl/5.32 /usr/share/perl/5.32 > /usr/local/lib/site_perl) at ./make_opengl line 3. > BEGIN failed--compilation aborted at ./make_opengl line 3. > make[1]: *** [debian/rules:125: override_dh_auto_configure] Error 2 I struggled to replicate this in sbuild or pbuilder with or without git-buildpackage until I added a Build-Conflicts on the package providing the `XML::LibXML` module which was apparently only pulled in as an alternative. So thanks for uncovering this issue changed upstream in 2017 that just happened to still work in Debian's resolvers. Thank you Mike for pushing to git, including the previous changes which I'd made for backports. I've pushed the new fix to `bookworm-wine7` branch and deleted the temporary emorrp1 branch. signature.asc Description: PGP signature
Bug#1021430: RFS: wine/7.0~repack-8~bpo11+1 -- Windows API implementation - standard suite
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "wine". See changelog or commit history for a few needed changes. I was planning to wait for libvulkan-dev to clear backports-NEW but apparently that's not necessary. It does need to go through NEW and bonus points if you're willing to add me to the DM list to allow future direct uploads: * Package name : wine Version : 7.0~repack-8~bpo11+1 Upstream contact : [fill in name and email of upstream] * URL : https://www.winehq.org * License : FSFAP, Public-Domain, LGPL-2.1+, Expat, Unicode * Vcs : https://salsa.debian.org/wine-team/wine Section : otherosfs The source builds the following binary packages: wine - Windows API implementation - standard suite wine32 - Windows API implementation - 32-bit binary loader wine64 - Windows API implementation - 64-bit binary loader wine32-preloader - Windows API implementation - prelinked 32-bit binary loader wine64-preloader - Windows API implementation - prelinked 64-bit binary loader wine32-tools - Windows API implementation - 32-bit developer tools wine64-tools - Windows API implementation - 64-bit developer tools libwine - Windows API implementation - library libwine-dev - Windows API implementation - development files wine-binfmt - Register Wine as the interpreter for Windows executables fonts-wine - Windows API implementation - fonts To access further information about this package, please visit the following URL: https://mentors.debian.net/package/wine/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/w/wine/wine_7.0~repack-8~bpo11+1.dsc Changes since the last upload: wine (7.0~repack-8~bpo11+1) bullseye-backports; urgency=medium . * Rebuild for bullseye-backports. * drop adapter_vk.c change from vulkan.patch * require libvulkan-dev newer than bullseye * add myself to Uploaders * omit dpkg (>= 1.21.0) constraint Regards, -- Phil Morrell signature.asc Description: PGP signature
Bug#1021422: RFS: vkd3d/1.2-15~bpo11+1 -- Direct3D 12 to Vulkan translation - shader compiler
mpiler in the dev package. Regards, -- Phil Morrell signature.asc Description: PGP signature
Bug#1021401: RFS: vulkan-loader/1.3.224.0-1~bpo11+1 -- Vulkan loader library -- development files
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "vulkan-loader". It is a trivial backport (dch --bpo) and does not need to go through NEW: * Package name : vulkan-loader Version : 1.3.224.0-1~bpo11+1 * URL : https://github.com/KhronosGroup/Vulkan-Loader * License : Apache-2.0, MIT * Vcs : https://salsa.debian.org/emorrp1/vulkan-loader/-/tree/debian/bullseye-backports Section : libs The source builds the following binary packages: libvulkan1 - Vulkan loader library libvulkan-dev - Vulkan loader library -- development files To access further information about this package, please visit the following URL: https://mentors.debian.net/package/vulkan-loader/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/v/vulkan-loader/vulkan-loader_1.3.224.0-1~bpo11+1.dsc Changes since the last upload: vulkan-loader (1.3.224.0-1~bpo11+1) bullseye-backports; urgency=medium . * Rebuild for bullseye-backports. . vulkan-loader (1.3.224.0-1) unstable; urgency=medium . * New upstream release. . vulkan-loader (1.3.216.0-1) unstable; urgency=medium . * New upstream release. . vulkan-loader (1.3.211.0-1) unstable; urgency=medium . [ Timo Aaltonen ] * New upstream release. * sync_headers.sh: Fix checking the version. * patches: Dropped, upstream. . [ Simon McVittie ] * tests: Exclude precompiled binary objects from .orig tarball * d/copyright: Update * Regenerate loader/generated/ during build. Thanks to Helmut Grohne (Closes: #981362) * d/rules: Delete another __pycache__ directory * d/libvulkan1.symbols: Expect i386 to be treated as an x86 architecture . vulkan-loader (1.3.204.1-2) unstable; urgency=medium . * symbols: Fix arch specific symbols. . vulkan-loader (1.3.204.1-1) unstable; urgency=medium . * New upstream release. * symbols: Fixed. . vulkan-loader (1.3.204.0-1) unstable; urgency=medium . * control: Drop python3-minimal dependency from libvulkan-dev. * New upstream release. * symbols: Updated. * symbols: Go back to a single symbols file, but skip some symbols on i386. . vulkan-loader (1.2.198.1-2) unstable; urgency=medium . * patches: Add patches to fix symbols for i386. (Closes: #1003219) * symbols: Add a symlink .aarch64 -> .amd64. . vulkan-loader (1.2.198.1-1) unstable; urgency=medium . * New upstream release. * sync_headers.sh: Updated to take sdk version as an argument, and use git checkout instead of force reset. * fix-ftbfs.diff: Dropped, upstream. * Drop prebuilt libdummy binaries from the source. * control: Add python dep to libvulkan-dev. . vulkan-loader (1.2.189.0-2) unstable; urgency=medium . * fix-ftbfs.diff: Fix a typo in a test. . vulkan-loader (1.2.189.0-1) unstable; urgency=medium . * New upstream release. Regards, -- Phil Morrell signature.asc Description: PGP signature
Bug#1021399: RFS: unicode-data/15.0.0-1~bpo11+1 -- Property data for the Unicode character set
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "unicode-data". It is a trivial backport (dch --bpo) and does not need to go through NEW: * Package name : unicode-data Version : 15.0.0-1~bpo11+1 * URL : https://www.unicode.org/ * License : Unicode-TOU * Vcs : https://salsa.debian.org/debian/unicode-data/-/tree/debian/bullseye-backports Section : misc The source builds the following binary packages: unicode-data - Property data for the Unicode character set To access further information about this package, please visit the following URL: https://mentors.debian.net/package/unicode-data/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/u/unicode-data/unicode-data_15.0.0-1~bpo11+1.dsc Changes since the last upload: unicode-data (15.0.0-1~bpo11+1) bullseye-backports; urgency=medium . * Rebuild for bullseye-backports. . unicode-data (15.0.0-1) unstable; urgency=medium . * New upstream release. Closes: #1019852 * Standards-Version: 4.6.1 Regards, -- Phil Morrell signature.asc Description: PGP signature
Bug#987244: RFS: nbsdgames/4.0-1 [ITP] -- text based mini games for your terminal
Hi tarzeau, as promised here's the policy violation details for this RFS. Despite the length, thank you for working on this, it seems to be a fun collection. > §10.1 https://www.debian.org/doc/debian-policy/ch-files.html#s-binaries > Two different packages must not install programs with different > functionality but with the same filenames. (The case of two programs > having the same functionality but different implementations is handled > via “alternatives” or the “Conflicts” mechanism. A different /usr/games/ PATH is not sufficient, nor is a Conflicts since the sos game bears no functional resemblance to the sos report command introduced as of bullseye. It is unclear to me whether this also applies to non-PATH executable filenames such as /usr/libexec/xscreensaver/pipes from xscreensaver-gl. Conflicting names appear to be handled on a first-come first-served basis for new packages and only go to tech-ctte if an unresolvable situation occurs after initial upload. Therefore, I believe sos must be renamed to comply with policy. > §7.4 > https://www.debian.org/doc/debian-policy/ch-relationships.html#s-conflicts > Be aware that adding Conflicts is normally not the best solution when > two packages provide the same files... > > Having similar functionality or performing the same tasks as another > package is not sufficient reason to declare Breaks or Conflicts with > that package. Similar functionality: * fifteen (sgt-puzzles) * mines (sgt-puzzles) * sudoku (sudoku) It is reasonable for a user to want to have all of sgt-puzzles, nbsdgames and kdegames (using a k prefix) installed simultaneously and play different subsets of the games available. This also allows the user to pick their favourite implementation where multiple exist. Given all this, I suggest you adopt a universal prefix for all the games, perhaps "nb-"? On the other hand, it might be worth preserving tab completion with a suffix instead, in which case no harm with a full "-nbsdgames". Additionally manpages are a "should" in §12.1 and there is interest from users, so please either write them or remember to open a request in the BTS. https://github.com/abakh/nbsdgames/issues/9 I'm working off Upload #6 from mentors and it still fails to build due to permission denied, this time with chown rather than cp. > dh_fixperms > chown root:games debian/nbsdgames/usr/games/* > chown: changing ownership of 'debian/nbsdgames/usr/games/battleship': > Operation not permitted signature.asc Description: PGP signature
Re: glmark2 debian package missing
On Mon, Jan 11, 2021 at 03:57:12PM +0200, Marius Vlad wrote: > Thanks for taking the time to comment on the matter. So, I guess I could > then step in. I've created myself an account on salsa. I have a couple > of questions, mostly related to the set-up of it: Excellent, I've granted you full access to the existing packaging repo. https://salsa.debian.org/games-team/glmark2 > - do I need to ask upstream to do a new release (I see the last one is > from April last year)? Is the policy to merge tags/release from upstream > then cherry-pick/rebase the local changes? Where can I find more info > about this? I guess the question is: 'How do we track and integrate > upstream changes?' It's currently setup for git-buildpackage with the upstream git history on branch "upstream", the tag merged into "master" which contains the debian/ folder. It's up to you how much you push for the latest version, tags are best but you can easily backport individual commits or use the git HEAD. https://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.import.upstream-git.html > - do I need to apply for some kind of Debian maintainer form? Maybe > create some kind of PGP key? Thought I've been a Debian user for years > I don't know how this works. That's fair enough, we all start somewhere and it can be daunting to make the move from user to package maintainer, but it is satisfying! I can see that your mail to me was already pgp-signed, which is great so you should register on mentors and upload your public key. https://mentors.debian.net/intro-maintainers/ > - @Phil, is there a way we could chat on IRC or something similar to get > things moving a bit faster than email. Of course. #debian-mentors is your best bet for asking packaging questions any time of day, but feel free to @emorrp1 if you like. The channel is also bridged to matrix at #_oftc_#debian-mentors:matrix.org Good luck! signature.asc Description: PGP signature
Bug#906536: Sponsor for my package "cavestory-nx"
(dropping list from CC) On Sun, Aug 26, 2018 at 05:04:36PM -0300, Carlos Donizete Froes wrote: > Hi, > > > You cannot just drop paragraphs from d/copyright at will, it needs to > > be backed up by a statement of the copyright owners. > > Sorry, I did not understand the previously replied email > and I ended up removing it. > Yes, you misunderstood me on this occasion. I tried to do two things: a) highlight that there was some desire from the author for NC license that needs confirming, e.g. maybe they want it to be CC-BY-NC? b) point out, as Tobi did, that you need some public documentation of the authors intent in order to document that in the copyright > > Can you, by change, forward the original statement of "pixel", on which > > basis you wrote d/copyright, to this bug/list? > > Yes, follows the forwarded message. What we're looking for here is an unambiguous public declaration of the license from Pixel. I'm afraid the forwarded email doesn't satisfy that. It's confusing regarding Cave Story/Vorbis and MIT/BSD and nothing in it mentions Public Domain. It seems theres some language barrier here, but first you need to find out what terms the author is after (I'm assuming here that it's art and not software), the most basic starting point is this: https://wiki.creativecommons.org/wiki/Considerations_for_licensors_and_licensees#Considerations_for_licensors Only after the author has decided on terms can they go about choosing a license, which may or may not be public domain, but if it is, there needs to be a clear public statement of that, e.g. the CC0 waiver I linked. signature.asc Description: PGP signature
Bug#906536: Sponsor for my package "cavestory-nx"
> > What changed since tobi's comment in May on the ITP bug? > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894865#30 > > I exchanged emails with the developer of the non-free files and had to make > corrections from the licenses and added a disclaimer about this package. I believe this is the problematic section of debian/copyright? I also found https://wiki.debian.org/DFSGLicenses#Public_Domain helpful. Files: data/* Copyright: not applicable Author: 2004 Studio Pixel License: public-domain This software was written by Daisuke Amaya also known by his art name 'Pixel'. . You absolutely can't use these in anything commercial; the work is not subject to copyright in any jurisdiction. . This file is in the public domain. It is provided "as is", without warranty of any kind. Use at your own risk. The second paragraph is self-contradicting - if it's not subject to copyright, then it's use can't be restricted to NC. Perhaps the author would prefer a different license? (any form of NC is still non-free) To avoid future disputes, after a private email conversation it is necessary to have a public record of the conclusion. Perhaps the author would be happy to email a CC0 style waiver: https://creativecommons.org/choose/zero/waiver * For public-domain "Copyright" line means who had the authority to license the work, i.e. the author, not "not applicable" * Since the full name is known, I would put that in the copyright line e.g Daisuke "Pixel" Amaya > > Why do you have 3 sponsorship-requests bugs open for the same package? > > Please close two of them and re-title the bug you leave open to the new > > version. > > Okay, I'll close these open requests. As well as closing 903872 & 905984 for the old version, it would help if 906536 blocks the ITP but lose the "[ITP]" in the subject. FWIW these days I don't bother with sponsorship-requests for games and just post directly to the mailing list and only if I get no response raise an RFS. -- Phil Morrell (emorrp1) signature.asc Description: PGP signature
Bug#880411: sqldeveloper-package version forking
On 19 November 2017 at 20:51, Adam Borowski wrote: >On Sun, Nov 19, 2017 at 04:55:42AM +, Lazarus Long wrote: >> The fact is that the NMU became a fork of an older version, that is out of, >> and irrelevant for, my timeline. > > Well, the history not having a record of a previous upload will confuse bug > version tracking. I think that, barring a manual intervention of setting a > "fixed" version in the bug that's a part of its current version history, > the bug will never go away. > > But I'm not sure what will happen. Yes, both the NMU and proposed-updates versions are forks, both of which are correctly recorded as Closes [868673]. As a result, if you click on the version graph and then "Don't ignore boring", both branches end in green and are also listed as "Fixed in versions". As for what will happen with v0.4.4, it would be nice if all the intermediary changelog entries were processed, but by the looks of [accepted], only the specifically uploaded one is. 20/20 hindsight therefore says v0.4.4 changelog should have included something like the following (split out according to this [guidance]): * Incorporates unreleased fixes now uploaded to unstable: - JVM path (Closes: #693798) - build error (Closes: #868673) - Included debhelper on the build dependency list (LP: #588458) - Replaced dh options with overrides (LP: #998258) [868673]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868673 [accepted]: https://tracker.debian.org/news/887940 [guidance]: https://lists.debian.org/debian-devel-announce/2003/06/msg00016.html I documented this partly for my own learning, but Lazarus please can you send the relevant metadata emails, or let me know you don't have time to? I believe this is all you need to fix the version graph (for each bug): "Control: fixed -1 0.4.4" (at top of email to 868673-done) https://www.debian.org/Bugs/server-control#fixed -- Phil Morrell (emorrp1)
Re: Comment posted on sqldeveloper-package
Hello Lazarus, pleased to meet you. I attempted to get in touch with you over the summer, but unfortunately only got bounces from bigfoot.com. On 29 October 2017 at 22:57, mentors.debian.net wrote: > Lazarus Long made the following comment about the sqldeveloper-package > package: > > Not sure what happened, but although I uploaded this package, it went under > Phil's name. > > I'm guessing it's an interface bug, and not a problem. If I'm wrong please > advise. I currently have an upload prepared for stretch-pu: https://bugs.debian.org/879850 I'm also guessing from the URL structure that there can be only one (first come, first served) uploader on mentors.debian.net per package but since your version was correctly signed, it was added to the existing page. If you like, I'm happy to reverse that by deleting the package page and re-uploading after you, just let me know. As for v0.4.2, thanks for fixing the outstanding bugs, I was only interested in getting it working on stretch and unfortunately I'm not at work today, so can't test the .deb. I did have to use dget --allow-unauthenticated on your .dsc otherwise dscverify complained about the signature, but gpg --verify did not. Hmm, dget-ing my own upload had the same issue - do I need to explicitly specify the keyring somehow, or is the 1024 bit key causing issues with gpg modern? In the changelog, please include my nmu entry verbatim (as it has reached unstable and instead of ack in 0.4.0), so bugs.debian.org correctly shows the graph for #868673. I don't know if the deb9u1 changelog entry also needs including, I've never done a stable update before. I also thought the changelog should only contain versions actually uploaded to unstable, rather than UNRELEASED ones, but that might just be the behaviour of git-buildpackage. As the package is debian native, does the VCS need to point to alioth? I know it's fine for there to be a mirror, accept contributions, or for the upstream to be on a non-free service, but I thought all the debian packaging needed to be DFSG hosted. Thanks, -- Phil Morrell (emorrp1)
Bug#879070: RFS: sqldeveloper-package/0.2.4+nmu1 [RC] [NMU]
Package: sponsorship-requests Severity: important Dear mentors, Would any of you consider sponsoring this NMU I prepared? It's a targeted one- line fix for #868673 which makes it unusable in Stretch. If possible I'd also like it in stretch-proposed-updates, presumably only after it's reached Buster? * Package name: sqldeveloper-package Version : 0.2.4+nmu1 Upstream Author : Lazarus Long * URL : https://tracker.debian.org/pkg/sqldeveloper-package * License : GPL-3+ Section : contrib/misc It builds those binary packages: sqldeveloper-package - Oracle SQL Developer Debian package builder To access further information about this package, please visit the following URL: https://mentors.debian.net/package/sqldeveloper-package Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/contrib/s/sqldeveloper- package/sqldeveloper-package_0.2.4+nmu1.dsc More information about sqldeveloper-package can be obtained from: https://manpages.debian.org/make-sqldeveloper-package Changes since the last upload: sqldeveloper-package (0.2.4+nmu1) UNRELEASED; urgency=medium * Non-maintainer upload. * Add required '--' before debian/rules target (Closes: #868673) * Add --no-tgz-check as sqldeveloper is non-free -- Phil Morrell Mon, 31 Jul 2017 13:16:50 +0100 -- System Information: Debian Release: 9.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Re: Request for sponsor for Stendhall Installer
Hello Carlos, As this is an initial release, have you considered using game-data-packager (if default-jre can be considered a game engine)? It think it would avoid proliferation of simple download wrappers, easing maintenance of e.g. menu entries and would also make the game available to all users on the system. Regards, Phil Morrell
