Re: How to contribute ?

On Tue, Dec 21, 2021 at 07:47:47PM +0100, Maxime Lombard wrote: > Hello, > > I'm an user of Debian since 10 years ago and it's only now that i decide to > help to packaging. > I send this email about wine and wine-development package which are not > updated since a very long time. Normally you sho

Re: How to contribute ?

On Fri, Dec 31, 2021 at 03:37:05PM +0100, Maxime Lombard wrote: > vkd3d 1.2-6 in Experimental is not usable in Sid because it needs > mesa-vulkan-driver << 21. > > Michael did that because vkd3d tests fails during building. I don't know > why because it fails with mesa 20 too. > > I opened a bug

Re: How to contribute ?

On Fri, Dec 31, 2021 at 02:47:22PM -0600, Zebediah Figura wrote: > > > vkd3d 1.2-6 in Experimental is not usable in Sid because it needs > > > mesa-vulkan-driver << 21. > > > > > > Michael did that because vkd3d tests fails during building. I don't know > > > why because it fails with mesa 20 too.

Re: DD(s) to help DM land some long-overdue package updates?

On Sat, Jan 01, 2022 at 07:06:09PM +, Reuben Thomas wrote: > Here's a summary of the packages I'm trying to update. If any DD can help me > get these uploaded, I'd be most grateful The packages you listed are not orphaned and the changes you listed don't warrant NMUs so your only options are ei

Re: How to contribute ?

On Sun, Jan 02, 2022 at 11:07:10AM -0600, Zebediah Figura wrote: > > > > > vkd3d 1.2-6 in Experimental is not usable in Sid because it needs > > > > > mesa-vulkan-driver << 21. > > > > > > > > > > Michael did that because vkd3d tests fails during building. I don't > > > > > know > > > > > why bec

Re: generic viewer for md files

On Mon, Jan 24, 2022 at 10:36:50AM +0100, Jerome BENOIT wrote: > is there a virtual package for viewing MD documents Do you mean Markdown? Are there specialized viewers for it at all? -- WBR, wRAR signature.asc Description: PGP signature

Re: generic viewer for md files

On Mon, Jan 24, 2022 at 12:46:40PM +0100, Jerome BENOIT wrote: > I am asking because a software that I am currently packaging has its documents > in MarDown (GitHub flavour, I guess). You can likely read those with `less`. Alternatively, software is likely to ship a build script for e.g. HTML in wh

Re: Unplanned freeze?

On Fri, Jan 28, 2022 at 07:53:02AM +0100, Ole Streicher wrote: > I just observed that many of my packages that are currently in unstable > are not migrating because of > > | Not touching package due to block request by elbrus (Follow the freeze > | policy when applying for an unblock) > > where t

Re: Legal advice regarding the NEW queue

On Tue, Feb 01, 2022 at 09:18:07AM -0800, Russ Allbery wrote: > I would hate to entirely lose the quality review that we get via NEW, but > I wonder if we could regain many those benefits by setting up some sort of > peer review system for new packages that is less formal and less > bottlenecked on

Re: Legal advice regarding the NEW queue

On Wed, Feb 02, 2022 at 11:39:11AM -0500, The Wanderer wrote: > >>> I would hate to entirely lose the quality review that we get via > >>> NEW, but I wonder if we could regain many those benefits by > >>> setting up some sort of peer review system for new packages that > >>> is less formal and less

Re: Legal advice regarding the NEW queue

On Wed, Feb 02, 2022 at 12:12:30PM -0500, Michael Stone wrote: > On Wed, Feb 02, 2022 at 11:39:11AM -0500, The Wanderer wrote: > > Doesn't that, then, lead to the suggestion that any package entering > > unstable without having undergone NEW review (which, in the revised > > model, might be every n

Re: What are the most important projects that Debian ought to work on?

On Wed, Feb 09, 2022 at 03:23:38PM +0100, Enrico Zini wrote: > > That's where you come into play: it would be nice if you could share > > what are — according to you — the most important projects/improvements > > that Debian ought to make. You can share your ideas here by replying to > > this email

Re: What are the most important projects that Debian ought to work on?

On Wed, Feb 09, 2022 at 06:53:49PM +0100, Enrico Zini wrote: > > > I've added "We should have a default standard packaging workflow": > > > https://salsa.debian.org/debian/grow-your-ideas/-/issues/24 > > This should include ideas what to do with resignations that will follow. > > Why would one dec

Re: What are the most important projects that Debian ought to work on?

On Thu, Feb 10, 2022 at 12:07:24PM +0100, dude wrote: > provide build in easy feedback-communications to digest, collect, analyze > user's needs and progress from there > > (more security, stability and faster boot is laways better X-D (in that > order)) > > aka: what is REALLY needed (comes per

Re: LESS copyright, not more!

On Thu, Feb 10, 2022 at 12:14:40PM +0100, dude wrote: > Linus: the (GPL 2.0) intented social contract is: “i give you sourcecode, > give me back your changes” > > https://dwaves.de/2022/01/31/why-is-it-gnu-linux-and-not-just-linux-linus-talking-about-gpl-v3-vs-gpl-v2-the-better-one-the-social-gpl-

Re: Why? "Marked for autoremoval on 24 March due to xdelta3: #965883"

On Thu, Feb 24, 2022 at 10:09:23PM +0900, Osamu Aoki wrote: > Hi, > > I favor moving away from pre-dh7 packages and I support people pushing for > it. But I > am in intriguing situation with this effort. Can someone help me. > > At: https://udd.debian.org/cgi-bin/autoremovals.cgi > > I see: >

Re: Bits from the Release Team: bookworm freeze dates (preliminary)

On Mon, Mar 14, 2022 at 09:43:15PM +0100, Jérémy Lal wrote: > > We are currently considering the following dates as our freeze > > dates. If you are aware of major clashes of these dates with anything > > we depend on please let us know. We also like to stress again that we > > really would like to

Re: proposed MBF: packages still using source format 1.0

On Tue, Mar 15, 2022 at 08:54:50AM +, Matthew Vernon wrote: > It's probably unfashionable, but I think debian/patches is not a great > way to manage changes, particularly if you're using a VCS for > maintaining your packages. As others have pointed out in this thread, > doing this means you end

Re: proposed MBF: packages still using source format 1.0

On Tue, Mar 15, 2022 at 10:49:17AM +, Matthew Vernon wrote: > >> It's probably unfashionable, but I think debian/patches is not a great > >> way to manage changes, particularly if you're using a VCS for > >> maintaining your packages. As others have pointed out in this thread, > >> doing this m

Re: isa-support -- exit strategy?

On Fri, Mar 25, 2022 at 11:34:17PM +0100, Adam Borowski wrote: > While packages are allowed to not support entire architectures > outright, there's a problem when some code requires a feature that is > not present in the arch's baseline. Effectively, this punishes an arch > for keeping compatibili

Re: What to do with merged /usr and dpkg-fsys-usrunmess

On Wed, Apr 06, 2022 at 04:02:23PM +0200, Bjørn Mork wrote: > > Sorry, blame the dpkg maintainer. > > Is that how we discuss technical issues around here? This is not a technical issue. -- WBR, wRAR signature.asc Description: PGP signature

Re: rebuild of rpcbind (and other packages?) due to old debhelper bug 993316

On Fri, Apr 08, 2022 at 03:22:07PM +0200, Vincent Lefevre wrote: > Due to the old bug 993316 in debhelper[*], rpcbind is still buggy as > it hasn't been rebuilt yet: rpcbind_1.2.6-2_amd64.deb contains > > -rw-r--r-- root/root 626 2021-08-17 17:31:36 > ./usr/lib/systemd/system/rpcbind.servic

Re: rebuild of rpcbind (and other packages?) due to old debhelper bug 993316

On Fri, Apr 08, 2022 at 05:25:11PM +0200, Vincent Lefevre wrote: > > > Bug 993316 was fixed on 23 September 2021. Any reason why rpcbind > > > hasn't been rebuilt yet? > > Was anything done for that to happen? Because otherwise the answer is > > "nobody did that". > > I would have assumed that thi

Re: ITP: trbot -- Powerful software for playing games through text, supporting remote collaborative play

On Fri, Apr 15, 2022 at 09:21:20PM +, kimim...@posteo.net wrote: > Package: trbot > Version: 2.5.1 > Severity: wishlist Looks like you intended to submit this as a bug report but sent it to debian-devel@ instead. Also, if you are not going to package and maintain this software in Debian but jus

Re: Firmware - what are we going to do about it?

On Tue, Apr 19, 2022 at 10:22:15AM +0200, parodper wrote: > > 5. We could split out the non-free firmware packages into a new > > non-free-firmware component in the archive, and allow a specific > > exception > > only to allow inclusion of those packages on our official media. We > >

Re: Firmware - what are we going to do about it?

On Tue, Apr 19, 2022 at 11:33:30AM +0200, Christian Kastner wrote: > Hi Steve, > > thank you for bringing this up. > > On 2022-04-19 02:27, Steve McIntyre wrote: > > 1. Keep the existing setup. It's horrible, but maybe it's the best we can > > do? > > (I hope not!)> > > 2. We could just st

Re: Firmware - what are we going to do about it?

On Tue, Apr 19, 2022 at 02:38:03PM +0200, Jonas Smedegaard wrote: > When I install systems, I consider non-free blobs more risky than other > code. Do you consider loadable non-free blobs more risky than their older versions soldered onto the hardware? > When I (sometimes, but not always¹) choos

Re: Firmware - what are we going to do about it?

On Tue, Apr 19, 2022 at 04:30:44PM +0100, Tim Woodall wrote: > > On Tue, Apr 19, 2022 at 02:38:03PM +0200, Jonas Smedegaard wrote: > > > When I install systems, I consider non-free blobs more risky than other > > > code. > > Do you consider loadable non-free blobs more risky than their older > > ve

Re: Firmware - what are we going to do about it?

On Tue, Apr 19, 2022 at 06:51:16PM +0200, Jonas Smedegaard wrote: > > > > > When I install systems, I consider non-free blobs more risky > > > > > than other code. > > > > Do you consider loadable non-free blobs more risky than their > > > > older versions soldered onto the hardware? > > > > > >

Re: Firmware - what are we going to do about it?

On Tue, Apr 19, 2022 at 11:00:23PM +0200, Jonas Smedegaard wrote: > > > > > > > When I install systems, I consider non-free blobs more risky > > > > > > > than other code. > > > > > > Do you consider loadable non-free blobs more risky than their > > > > > > older versions soldered onto the hardwa

Re: Keep both images but stop pretending no-free is unofficial

On Wed, Apr 20, 2022 at 12:55:44PM +0530, Pirate Praveen wrote: > >> Similarly, I think it would be reasonable for someone to want to provide > >> entirely free Debian media along with a libre laptop. > > > >Does this exist in the real world? Which hardware would such a system > >contain? > > lib

Re: Keep both images but stop pretending no-free is unofficial

On Wed, Apr 20, 2022 at 01:25:31PM +0530, Pirate Praveen wrote: > >> >> Similarly, I think it would be reasonable for someone to want to provide > >> >> entirely free Debian media along with a libre laptop. > >> > > >> >Does this exist in the real world? Which hardware would such a system > >> >co

Re: Keep both images but stop pretending no-free is unofficial

On Wed, Apr 20, 2022 at 08:28:25AM -0400, Polyna-Maude Racicot-Summerside wrote: > I think you lack pretty much of seeing more than you own self and use case. No, everything I write in these threads I write for our potential users who don't have enough knowledge to find things they need or to dismi

Re: Firmware - what are we going to do about it?

On Wed, Apr 20, 2022 at 05:04:13AM -0500, Devin Prater wrote: > So then, I found the Non-free section and got the CD version? I guess > that's what I should have gotten? The DVD one is the live environment > right? See how confusion this can be? Yes, the variety of our ISOs and the poor way they a

Re: Firmware - what are we going to do about it?

On Wed, Apr 20, 2022 at 12:53:46PM -0500, Devin Prater wrote: > But back on topic, would the nonfree DVD ISO's have more firmware on them > than the CD version? Or is that just for offline installs? As far as I understand it there is just one set of non-free firmware for including in the ISOs and s

Re: Firmware - what are we going to do about it?

On Thu, Apr 21, 2022 at 09:57:36AM +0300, Hakan Bayındır wrote: > As everybody knows, Debian is also releasing the said firmware as compressed > archives and these are visible in the download page [0], however usage and > documentation is neither clearly documented, nor easy for the beginners or >

Re: Firmware - what are we going to do about it?

On Thu, Apr 21, 2022 at 10:57:47AM +0300, Hakan Bayındır wrote: > > > As everybody knows, Debian is also releasing the said firmware as > > > compressed > > > archives and these are visible in the download page [0], however usage and > > > documentation is neither clearly documented, nor easy for

Re: Firmware - what are we going to do about it?

On Thu, Apr 21, 2022 at 01:39:39PM +0300, Hakan Bayındır wrote: > > > > > As everybody knows, Debian is also releasing the said firmware as > > > > > compressed > > > > > archives and these are visible in the download page [0], however > > > > > usage and > > > > > documentation is neither clearl

Re: Firmware - what are we going to do about it?

On Sat, Apr 23, 2022 at 03:13:29PM +0200, Paul van der Vlis wrote: > > I see several possible options that the images team can choose from here. > > However, several of these options could undermine the principles of Debian. > > We > > don't want to make fundamental changes like that without the c

Re: Firmware - what are we going to do about it?

On Sat, Apr 23, 2022 at 10:48:03PM +0200, Paul van der Vlis wrote: > > > I have an idea for an extra option: > > > > > > 6. Put the closed source firmware somewhere in the Debian images, but > > > never > > > install closed source firmware by default. "No" should be the default. > > That's the op

Re: Firmware - what are we going to do about it?

On Sun, Apr 24, 2022 at 05:03:29AM +0200, Simon Richter wrote: > > Making Debian hard to use is a very short-sighted view of how to promote > > free software - it works in the very short term only. > > The same applies in the other direction -- making no real distinction > between free and non-fre

Re: Firmware - what are we going to do about it?

On Mon, Apr 25, 2022 at 05:53:03PM +0200, Paul van der Vlis wrote: > > > > > I have an idea for an extra option: > > > > > > > > > > 6. Put the closed source firmware somewhere in the Debian images, but > > > > > never > > > > > install closed source firmware by default. "No" should be the defaul

Re: Firmware - what are we going to do about it?

On Tue, Apr 26, 2022 at 11:59:20AM +0300, Hakan Bayındır wrote: > > No, they do not. Most popular devices won't work at all without non- > > free firmware, including boring things such as mass storage (SD cards, > > SSD, HDD, ..., and controllers), input devices (keyboards, mice, ...). > > Yeah, y

Re: rules-needs-root: yes (Was: popularity-contest: support for XB-Popcon-Reports: no)

On Thu, May 05, 2022 at 11:31:37AM +0200, Andreas Tille wrote: > > If there's a growing list of boolean control fields, isn't it the > > indication that some sort of tagging system might make more sense? > > > > Instead of three lines: > > > > XB-Popcon-Reports: no > > Rules-Requires-Root: yes >

Re: Correct version and revision of upstream packaged Debian package

On Fri, May 20, 2022 at 10:22:55AM +0300, Tuukka Pasanen wrote: > After reading couple times Debian Policy documentation packaging conventions > and especially'5.6.12.2. Special version conventions' chapter. I'm bit > confused about revision system. As MariaDB Foundation wants to provide > upstream

Re: Correct version and revision of upstream packaged Debian package

On Fri, May 20, 2022 at 10:52:08AM +0200, Jonas Smedegaard wrote: > > It only makes sense to use '+maria~deb11' if you are going to > > also release '+maria' that needs to sort after all of those, or if you are > > using/going to use some '+maria+foo' scheme(s) that, again, need to sort > > after a

Re: Concerns about Security of packages in Debain OS and the Operating system itself.

On Mon, May 23, 2022 at 07:22:40PM +0100, lkcl wrote: > > > i believe the answer is in the question. debian is based on distributed > > > trust. i did the analysis (took 3 weeks): it is literally the only > > > distro in the world with an inviolate chain of trust from a large keyring > > > dati

Re: Project Improvements

On Wed, May 25, 2022 at 08:21:03PM +0200, David Kalnischkies wrote: > > I support many people with Debian, what I often see is that they remove a > > package, and then also the meta-package is removed. And later all > > dependencies of the meta-package are removed by accident. > > Not to rain on y

Re: Project Improvements

On Thu, May 26, 2022 at 03:28:21PM +0500, Andrey Rahmatullin wrote: > > > I support many people with Debian, what I often see is that they remove a > > > package, and then also the meta-package is removed. And later all > > > dependencies of the meta-package are remo

Re: maildir-utils is marked for autoremoval from testing

On Thu, May 26, 2022 at 04:54:25PM +0200, Hector Oron wrote: > > > maildir-utils 1.6.10-1 is marked for autoremoval from testing on > > 2022-06-30 > > > > > > It (build-)depends on packages with these RC bugs: > > > 1011146: nvidia-graphics-drivers-tesla-470: CVE-2022-28181, > > CVE-2022-28183, CVE

Re: cups-pdf is marked for autoremoval from testing

On Thu, May 26, 2022 at 02:33:20PM +0300, Martin-Éric Racine wrote: > Someone apparently made a commit to the autoremoval hinter that makes > it mark packages unrelated to an RC-bug package getting marked for > autoremoval. That's not what has happened. > Could someone please look into this? The b

Re: 1011146: nvidia-graphics-drivers-tesla-470 is a dependency of libb2

No, see https://bugs.debian.org/1011268 (already linked in the bug report you replied to). -- WBR, wRAR signature.asc Description: PGP signature

Re: Project Improvements

On Thu, May 26, 2022 at 06:47:19PM +0200, David Kalnischkies wrote: > > > > > I support many people with Debian, what I often see is that they > > > > > remove a > > > > > package, and then also the meta-package is removed. And later all > > > > > dependencies of the meta-package are removed by ac

Re: Firmware - what are we going to do about it?

On Sun, May 29, 2022 at 05:33:21PM -0400, Bobby wrote: > There are definitely people who use forks because it's easier to > install non-free firmware. What's the problem with that? Let them use > forks. A distro can't be all things to all people. This would mean almost officially dropping support

Re: use of Recommends by vlc to force users to use pipewire

On Tue, May 31, 2022 at 10:55:55AM +0200, Vincent Lefevre wrote: > > > a) pipewire package enables pipewire service by default > > > > Indeed, but pipewire service doesn't take control of audio over > > pulseaudio. Only pipewire-pulse does that. > > This is incorrect. The pipewire-pulse package

Re: use of Recommends by vlc to force users to use pipewire

On Tue, May 31, 2022 at 11:43:06AM +0200, Vincent Lefevre wrote: > > > > > a) pipewire package enables pipewire service by default > > > > > > > > Indeed, but pipewire service doesn't take control of audio over > > > > pulseaudio. Only pipewire-pulse does that. > > > > > > This is incorrect. The

Re: Python installation paths

On Thu, Jun 02, 2022 at 07:19:56PM +0200, Alec Leamas wrote: > Dear list, > > I try handle a package which installs a partly compiled, > architecture-dependent python module. Until now this has been done in > /usr/lib/triplet/python3.10/site-packages. This scheme has basically worked > fine. > >

Re: Python installation paths

On Thu, Jun 02, 2022 at 09:15:40PM +0200, Alec Leamas wrote: > > > I try handle a package which installs a partly compiled, > > > architecture-dependent python module. Until now this has been done in > > > /usr/lib/triplet/python3.10/site-packages. This scheme has basically > > > worked > > > fin

Re: Bug#1013132: ITP: BabaSSL -- BabaSSL is a base library for modern cryptography and communication security protocols.

On Wed, Jun 22, 2022 at 02:21:43PM +, Lance Lin wrote: > > AFAIK this library is forked from OpenSSL with some extensive > > modifications to support new crypto technologies, do you think we need > > to involve the Security Team to review whether this package can be > > supported during the nex

Re: Package uploads silently discarded: how to investigate?

On Mon, Jun 27, 2022 at 09:02:30AM +1000, Ben Finney wrote: > In this thread I want to discover: How can I find out what's happening > and why the Debian archive is no longer sending me any email messages > about my package uploads? You should check usper.debian.org:/srv/upload.debian.org/queued/ru

Re: Lintian breaks existing lintian-overrides due to added []

On Wed, Jun 29, 2022 at 02:49:35PM +0200, Andreas Tille wrote: > Hi, > > I realised that lintian (at least) starting with version 2.115.1 (may be > earlier) wraps file names into [] which breaks existing > lintian-overrides. Random example: > > > https://salsa.debian.org/med-team/biomaj3-user

Re: Bug#1013132: ITP: BabaSSL -- BabaSSL is a base library for modern cryptography and communication security protocols.

On Wed, Jun 29, 2022 at 01:43:25PM +, Lance Lin wrote: > Hello everyone, > > Thank you for your input and guidance. I've only been in Debian for a year so > > I still have many things to learn. I assumed there would be issues with > library > name conflicts and wanted to get the group's opi

Re: is rust-failure a heisen-package?

On Thu, Jun 30, 2022 at 02:35:45PM +0200, Jonas Smedegaard wrote: > Hi, > > This looks odd to me: https://tracker.debian.org/pkg/rust-failure > > Latest news from 7 months ago was *removal* of the package, yet it is > seemingly still around. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=97329

Re: Bug#1014908: ITP: gender-guesser -- Guess the gender from first name

On Thu, Jul 14, 2022 at 08:45:24AM -0400, Roberto C. Sánchez wrote: > > > > And I see you uploaded ~immediately - why even bother with an ITP? > > > > > > Is it proper procedure to upload without an ITP? > > > > > > > No ; I have to admit a large percentage of the new packages I upload > > get t

Re: how about telegram channel

On Wed, Jul 20, 2022 at 12:37:25PM +0200, Rand Pritelrohm wrote: > You can also keep a session open if you have a small SOC/board around > (screen tmux are her for that) without BNC/ZNC honeypot things. Seriously. > No need for those fancy, bloated, full of javascript modern things > blinking like

Re: how about telegram channel

On Wed, Jul 20, 2022 at 11:09:57AM +0200, Pierre-Elliott Bécue wrote: > I'd try to stay closer to FOSS decentralized solution like Mattermost or > Rocket Chat (not sure how and if it evolved to the point of being > usable). Shouldn't this have gone to -curiosa instead? -- WBR, wRAR signature.as

Re: debhelper-compat should allow >= relations

On Sat, Jul 30, 2022 at 11:15:30AM -0700, Dima Kogan wrote: > Hi. This probably has been covered before It wasn't, but it's completely identical to putting 13 into debian/compat, which never supported >= either. > This works fine if you're building for Debian/sid in 2022. It does not > work in any

Re: debhelper-compat should allow >= relations

On Sat, Jul 30, 2022 at 10:21:06PM -0700, Dima Kogan wrote: > > it's completely identical to putting 13 into debian/compat > > Oh. So it is. I vaguely remember that using debian/compat and > "Build-Depends: debhelper" generated some lintian complaints. Using debian/compat and "Build-Depends: debhe

Re: Unsolicited GNU bc patch

On Sat, Aug 06, 2022 at 05:12:13AM +, Thomas DiModica wrote: > Yes, I keep spamming this trying to find an appropriate mailing list. I don't > remember how or why I initially stumbled across this bug report > (https://bugs.launchpad.net/ubuntu/+source/bc/+bug/1775776), but, given that > I have

Re: Automatic trimming of changelogs in binary packages

On Fri, Aug 19, 2022 at 11:44:03AM +, Bastien Roucariès wrote: > Le jeudi 18 août 2022, 19:18:35 UTC Gioele Barabucci a écrit : > > Hello, > > > > in 2020 there was a brief discussion on debian-devel@ about trimming > > changelogs [1,2]. > > > > Now there is a working implementation of said f

Re: Comments on proposing NEW queue improvement (Re: Current NEW review process saps developer motivation

On Fri, Aug 26, 2022 at 04:13:43PM -0400, M. Zhou wrote: > If one's enthusiasm on working on some package is eventually > worn out after a break, then try to think of the following question: > > Is it really necessary to introduce XXX to Debian? > Must I do this to have fun? > > Strong motiva

Re: Need a buildd build after trip through NEW -- best practice?

On Sun, Aug 28, 2022 at 05:54:36PM -0500, Steven Robbins wrote: > I understand that the current state is that one can only "give back" a failed > build. I'm asking whether this must necessarily be the case. Yes, by definition. > Specficially: in the case of a NEW binary upload, could a manual

Re: Bug#1018759: ITP: sd - intuitive find and replace CLI

On Tue, Aug 30, 2022 at 06:44:36PM +0800, Blair Noctis wrote: > An RFP is at #1016929 [1]. > > 1: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016929 > You should have retitled and owned the RFP instead of creating a separate ITP. Y

Re: Re: Need a buildd build after trip through NEW -- best practice?

On Thu, Sep 01, 2022 at 08:45:06AM -0500, Steven Robbins wrote: > > > Specficially: in the case of a NEW binary upload, could a manual request > > > be > > > implemented (pick a different name if "give back" is not suitable) such > > > that it is thrown away and replaced by a buildd build? > > > >

Re: Half the world being removed

On Thu, Sep 01, 2022 at 11:04:38PM -0500, Steven Robbins wrote: > Suddenly half the packages are marked AUTOREMOVE; many due to gcc-12 and > zlib. > The related two bugs are months-old. > > Why are things suddenly being removed?? Both are key packages per https://udd.debian.org/cgi-bin/key_pa

Re: Automatic trimming of changelogs in binary packages

On Tue, Sep 06, 2022 at 12:11:38PM +0300, Hakan Bayındır wrote: > While all looks good and feels sound from many aspects, I have some > reservations against treating changelogs as metadata. > > Current changelogs as files have a well known place, can be used by anything > and everything, and they

Re: Intel CET Support?

On Mon, Sep 05, 2022 at 10:44:52PM +0200, Felix Potthast wrote: > i just stumbled upon the fact that debian doesn't yet make use of the > Intel CET security feature, while many other distributions > (Ubuntu, Fedora, Suse, Arch Linux) do. > > The idea is to insert endbr instructions, > (which are j

Re: Automatic trimming of changelogs in binary packages

On Sun, Sep 11, 2022 at 02:41:24PM +0300, Hakan Bayındır wrote: > > On Tue, Sep 06, 2022 at 12:11:38PM +0300, Hakan Bayındır wrote: > >> While all looks good and feels sound from many aspects, I have some > >> reservations against treating changelogs as metadata. > >> > >> Current changelogs as fi

Re: Automatic trimming of changelogs in binary packages

On Sun, Sep 11, 2022 at 03:09:07PM +0300, Hakan Bayındır wrote: > Stuffing them behind a command, possibly making them online only in the > process will arguably make system troubleshooting and administration > harder, > esp. if the system has connectivity issues. > > >>>

Re: transition to usrmerge to start around 2022-09-15 (next Thursday)

On Sun, Sep 18, 2022 at 11:16:22AM +0200, Bjørn Mork wrote: > I find it quite disappointing to read https://bugs.debian.org/848622 . I > don't know if it is arrogance or ignorance, but this bug is undoubtedly > caused by usrmerge: > > frtest2:~# ls -l /usr/bin/bash > -rwxr-xr-x 1 root root 1283

Re: my package uploads silently rejected

On Wed, Nov 30, 2022 at 03:03:14PM +0100, Jonas Smedegaard wrote: > I have tried ssh into the host ssh.upload.debian.org and (after fumbling > around) found the file /srv/upload.debian.org/queued/run/log where I see > only succesful notices about rust-criterion, no indication of rejection. The seco

Re: Migration bug ?

On Mon, Dec 12, 2022 at 07:28:27AM +0100, Yadd wrote: > Hi, > > I pushed 2 versions of node-rollup since December 09, but migration process > never started (at least looking at tracker.d.o). Is there something broken ? > > Cheers, > Yadd > > https://tracker.debian.org/pkg/node-rollup Note that t

Re: DEB_BUILD_OPTIONS=nowerror

On Fri, Feb 24, 2023 at 08:27:53AM +0100, Helmut Grohne wrote: > > Also I think it was recommended to *not* use -Werror by default as it > > is too fragile. Maybe one should have a "developer mode" flag instead > > that allows using -Werror? > > Well, if we were avoiding -Werror by default, we wou

Re: need GBP help with groff 1.23.0 (1.23.0~rc3-1 package prepared)

On Sun, Feb 26, 2023 at 12:06:18AM -0600, G. Branden Robinson wrote: > Background: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011666 > > Can someone advise me as to the correct procedure for merging upstream > release candidate archives into https://salsa.debian.org/debian/groff ? Just imp

Re: Reducing allowed Vcs for packaging?

On Sun, Feb 26, 2023 at 02:24:26PM +0100, Bastian Germann wrote: > During the last weeks I had a look at the Vcs situation in Debian. Currently, > there are eight possible systems allowed I see a difference between (dis)allowing a VCS in the Vcs-* fields and (dis)allowing maintainers to store packa

Re: Bug#1031548: FTBFS with ruby-jekyll-github-metadata 2.15.0

On Sun, Feb 26, 2023 at 09:20:13PM +0100, Daniel Leidert wrote: > > > > Debian Policy §4.9 says that *attempting* to access the internet > > > > is forbidden: > > > > > > > >   For packages in the main archive, required targets must not > > > > attempt > > > >   network access, except, via the loo

Re: a naive question about EOL encoding in Debian

On Sat, Mar 18, 2023 at 08:45:37PM +0100, Patrice Duroux wrote: > Hi, > > I am facing ^M (\r) character in the .build output file using sbuild > on my system (Sid). > For instance: > > $ file timidity_2.14.0-9_amd64-2023-03-18T18:33:37Z.build > timidity_2.14.0-9_amd64-2023-03-18T18:33:37Z.build:

Re: source only upload with git-buildpackage

On Sat, Oct 05, 2019 at 08:06:56PM +0200, Alf Gaida wrote: > that is miss something - my point is: Why do you invoke pbuilder (read > the same question about sbuild too) to create pure source packages? To make sure they build correctly. -- WBR, wRAR signature.asc Description: PGP signature

Re: source only upload with git-buildpackage

On Sat, Oct 05, 2019 at 10:02:54PM +0200, Alf Gaida wrote: > >> that is miss something - my point is: Why do you invoke pbuilder (read > >> the same question about sbuild too) to create pure source packages? > > To make sure they build correctly. > > > Ok, checked the calender, it is not April 1. I

Re: [RFC] Proposal for new source format

On Wed, Oct 23, 2019 at 09:49:11AM -0400, Theodore Y. Ts'o wrote: > > > That seems excessively pessimistic. What about Git makes you think > > > it's impossible to create a reproducible source package? > > > > Has it been done? Given this point has been raised several times > > before if it hasn

Bug#944902: ITP: python-protego -- pure-Python robots.txt parser with support for modern conventions

Package: wnpp Severity: wishlist Owner: Andrey Rahmatullin * Package name: python-protego Version : 0.1.15 Upstream Author : Anubhav Patel et al. * URL : https://github.com/scrapy/protego * License : BSD-3 Programming Lang: Python Description : pure

Re: About license compatibility

On Fri, Dec 06, 2019 at 12:10:30AM +0900, JungHwan Kang wrote: > I know Debian has GPLv2. This is most likely not true, depending on what do you mean by that. > There are many packages having a different license in the Debian distribution. > How to resolve a conflict between licenses to specify GP

Re: About license compatibility

On Thu, Dec 05, 2019 at 10:57:43AM -0500, Boyuan Yang wrote: > > For instance, GPLv2 & GPLv3 are incompatible. > > I never heard that GPLv2 license and GPLv3 license are incompatible. They are. https://www.gnu.org/licenses/gpl-faq.html#v2v3Compatibility You may be thinking about upgrading GPLv2+ t

Re: difficulty in understanding options in init-system-GR

On Sat, Dec 07, 2019 at 11:45:36AM +0100, Marco d'Itri wrote: > > The rest options, i.e. B A D H G, look nearly the same to me: > > "first tier support for systemd, second tier for others" > > The only difference I noted is the bug severity for non-systemd support. > > > > In which way(s) are op

Re: About license compatibility

On Sun, Dec 08, 2019 at 04:37:28PM +0900, JungHwan Kang wrote: > Thank you for your detailed answer. :) > I'm gonna ask one more question, please. I don't see a question below. > I was confused Ubuntu cannot have an overall license, because of the > license of Ubuntu as below. > "Ubuntu operates u

Re: Packaging text licenses

On Sat, Dec 14, 2019 at 05:22:09PM +0100, Francesco Poli wrote: > A number of license texts are not themselves licensed under DFSG-free > terms. > > And Debian promises to remain 100 % free, see [SC] #1. Any content of a > Debian package (in main) must be free according to the DFSG. Sure. > Licen

Re: Packaging text licenses

On Sun, Dec 15, 2019 at 09:05:19AM -0500, jrb3-beckenbach.us wrote: > A subset of the more general “can Debian core ship non-free *data*”. Officially no, as already mentioned in this thread. > Perhaps an argument this is really shipping a convenience *cache* of > freely-available read-only texts.

Re: Packaging text licenses

On Sun, Dec 15, 2019 at 02:25:47PM +0100, Jonas Smedegaard wrote: > As others in this thread have pointed out, Debian explicitly omits > classifying license fulltexts as "free software" or "non-free software". Where does it explicitly do that? We do that implicitly. -- WBR, wRAR signature.asc

Re: requirements and regulations concerning upgrade checks/statistics callback on program start

On Thu, Dec 26, 2019 at 08:48:44PM +0900, Norbert Preining wrote: > Yeah, agreed with you feeling, but I searched today the policy and > social contract etc etc, and I didn't find any regulation concerning it. There are lintian checks and I think that's all. Maybe it's time to document it in the Po

Re: requirements and regulations concerning upgrade checks/statistics callback on program start

On Thu, Dec 26, 2019 at 05:48:17PM +0500, Andrey Rahmatullin wrote: > On Thu, Dec 26, 2019 at 08:48:44PM +0900, Norbert Preining wrote: > > Yeah, agreed with you feeling, but I searched today the policy and > > social contract etc etc, and I didn't find any regulation concer

<    2   3   4   5   6   7   8   9   10   11   >