On Wed, May 28, 2025 at 01:53:21PM +0200, Julien Plissonneau Duquène wrote:
1. process new requests and give feedback instantly
My opinion now is that debbugs runs pretty frequently, but emails
get rejected randomly, leading to a 30min wait for mail queue
reruns. This is probably a mail serve
On Sun, May 25, 2025 at 01:02:25PM +0100, Colin Watson wrote:
It would be really nice if there was an easy way to link a bug report to a MR
on salsa
you can try
forwaded NN
https://salsa.debian.org/debian-team/package-name/-/merge_requests/MMM
but eg gmail will break the long line before
On Sun, May 25, 2025 at 10:56:14AM +0100, Richard Lewis wrote:
It would be really nice if there was an easy way to link a bug report to a MR
on salsa
you can try
forwaded NN
https://salsa.debian.org/debian-team/package-name/-/merge_requests/MMM
but eg gmail will break the long line befor
On Fri, May 23, 2025 at 09:57:05PM +0400, Alex Sklemin wrote:
Several years ago, I encountered an issue with the lack of drivers for a
COM mouse. While this may not be a common problem today, it was a critical
need in my case. Additionally, during my time as a system administrator in
Russian hosp
On Thu, May 22, 2025 at 02:30:13PM +0100, Jonathan Dowland wrote:
The formatting of this was mangled so I couldn't figure out which
parts of the mail were quotes and which weren't.
It's, again, related to format=flowed.
--
WBR, wRAR
signature.asc
Description: PGP signature
On Thu, May 22, 2025 at 12:52:29PM +0100, Colin Watson wrote:
Do you really enjoy waiting 30 min for a bug to be created to
get a bug number?
I agree there are a number of problems with debbugs, but I don't
think it's helpful to exaggerate quite so wildly. The cron job
that processes incomin
On Thu, May 22, 2025 at 12:00:05PM +0100, Colin Watson wrote:
Do you really enjoy waiting 30 min for a bug to be created to get a
bug number?
I agree there are a number of problems with debbugs, but I don't think
it's helpful to exaggerate quite so wildly. The cron job that
processes incomin
On Thu, May 22, 2025 at 11:36:50AM +0300, Hakan Bayındır wrote:
I also like bugreport, debbugs, and current workflow, and it follows
natural to me (considering I'm both experienced with Debian ecosystem
and nearing graybeard territory). However, the initial experience is a
bit disconcerting for
On Thu, May 22, 2025 at 10:54:21AM +0200, Marc Haber wrote:
What would help is a web ui built on top of debbugs, and made available to
anyone,
possibly by adding another link next to tracker.d.o bugs link.
That noone has done this yet is a sign for me that we don't actually
need it so urgently
On Tue, May 20, 2025 at 07:59:31PM +0500, Andrey Rakhmatullin wrote:
I'm deeply concerned that the "surface area" of Debian packaging
tools is too large already for new folk, and adding something like
gwh into the archive makes that problem worse.
Fair enough, although I'
On Tue, May 20, 2025 at 04:15:19PM +0200, Roland Mas wrote:
I'm deeply concerned that the "surface area" of Debian packaging
tools is too large already for new folk, and adding something like
gwh into the archive makes that problem worse.
Fair enough, although I'm hoping to make gwh good enough
On Tue, May 20, 2025 at 01:03:47PM +0200, Mechtilde Stehmann wrote:
I'm deeply concerned that the "surface area" of Debian packaging
tools is too large already for new folk, and adding something like
gwh into the archive makes that problem worse.
I would really like to see an effort to improve
On Tue, May 20, 2025 at 11:07:03AM +0100, Jonathan Dowland wrote:
I'm deeply concerned that the "surface area" of Debian packaging tools
is too large already for new folk, and adding something like gwh into
the archive makes that problem worse.
I would really like to see an effort to improve g
On Mon, May 19, 2025 at 05:50:08PM +0100, Richard Lewis wrote:
This is a wrapper script around git-buildpackage
so you have gwh, calling gbp, calling sbuild?, calling dpkg-buildpackage?,
calling debian/rules, calling dh, calling dh_auto_build?, calling upstream's
build system (which may itsel
On Mon, May 12, 2025 at 02:37:18PM -0700, Otto Kekäläinen wrote:
Using gbp pq is easy, and it is also backwards compatible with quilt,
and automatically uses DEP-3 headers
(some of them)
--
WBR, wRAR
signature.asc
Description: PGP signature
Sorry but most of this looks like expanding on what I've said but maybe
I've misunderstood something.
--
WBR, wRAR
signature.asc
Description: PGP signature
On Mon, May 12, 2025 at 11:58:45AM +0200, Santiago Vila wrote:
El 12/5/25 a las 9:49, Holger Levsen escribió:
I dont want to use git-buildpackage and I don't want a gpb.conf. Please accept
this. Thanks.
I also don't like the idea of adding a gpb.conf to each and every package.
Yes, in most c
On Mon, May 12, 2025 at 09:54:38AM +0200, Gioele Barabucci wrote:
Regardless of what branch names packages use today or in the future,
they should all have a debian/gbp.conf file that defines what branches
and packaging practices are being used *right now*.
I dont want to use git-buildpackage a
On Thu, May 08, 2025 at 08:46:35AM +, Holger Levsen wrote:
> > I think your reaction to this is a bit harsh. I see this ITN proposal as
> > a way how to handle pacakges that are effectively unmaintained, but
> > where one is not necessarily interested in becoming the maintainer.
> we have a p
On Thu, May 08, 2025 at 08:06:03AM +, Holger Levsen wrote:
I think your reaction to this is a bit harsh. I see this ITN proposal as
a way how to handle pacakges that are effectively unmaintained, but
where one is not necessarily interested in becoming the maintainer.
we have a procedure for
On Wed, May 07, 2025 at 08:43:24PM +0200, Simon Josefsson wrote:
I think we should give up on /usr/games and move those
executables to /usr/bin, renaming any binaries that conflict.
This seems somewhat off-topic for a discussion of FTBFS - I hope that
packages don't assume that /usr/games is in
On Mon, May 05, 2025 at 11:15:01AM -0400, Mo Zhou wrote:
More information can be found at:
https://www.debian.org/vote/2025/vote_002
I guess this is still in "discussion period"? When does that
period end and
the vote begin?
That's described in
https://www.debian.org/devel/constitution.en
On Sun, May 04, 2025 at 09:24:45PM -0500, Steven Robbins wrote:
More information can be found at:
https://www.debian.org/vote/2025/vote_002
I guess this is still in "discussion period"? When does that period end and
the vote begin?
That's described in
https://www.debian.org/devel/constituti
On Mon, Apr 28, 2025 at 01:50:19PM +0200, Daniel Gröber wrote:
Hi Marc,
On Mon, Apr 28, 2025 at 12:31:24PM +0200, Marc Haber wrote:
I was just told off-the-records that [...]
Consider the motives of those staying out of the public limelight.
Does consensus need to be spoken quietly and in th
On Mon, Apr 21, 2025 at 12:19:25AM -0500, Steven Robbins wrote:
On Sunday, April 20, 2025 7:50:07 p.m. Central Daylight Saving Time Steven
Robbins wrote:
I am able to reproduce it thanks to NoisyCoil's hint about
--aspcud-criteria. I'm working on a fix now.
Okay, I don't know how to solve thi
On Sun, Apr 20, 2025 at 06:25:53PM +0100, Josh Triplett wrote:
> > Debian trixie images ship with 'mawk' pre-installed right now. While
> > I'm not convinced the removal game is necessarily a good one, I can
> > see that it does have some advantages. Is it possible to drop 'mawk'
> > from the s
On Tue, Mar 18, 2025 at 07:23:33AM +0100, Salvo Tomaselli wrote:
I was also curious if somebody cares about it enough to fix those.
I only found out very recently that it's not in good state, because I was
installing debian 13 on a new device and couldn't find the package, so I figured
it must
On Wed, Mar 26, 2025 at 12:26:42PM +0530, Sarbjit Singh Sandhu wrote:
Thanks for your suggestion I liked that but can you please help me that how
to use and install debian on approx 20 computers of my schools with the kde
plasma desktop and how to update them every 2 years and also making it user
On Mon, Mar 17, 2025 at 12:03:57AM +0100, Salvo Tomaselli wrote:
Hello,
I am a user of telegram-desktop.
The maintainer seems MIA.
The package has 2 RC bugs and is FTBFS.
It also depends on cppgir which is RC-buggy.
I prevented removal of telegram-desktop from testing 4 or 5 times over the
On Sat, Mar 15, 2025 at 04:34:09PM -0400, Roberto C. Sánchez wrote:
Question: Should uncoordinated NMUs unilaterally choose Salsa as the VCS
for a package?
That doesn't make sense to me, at least without context, not because
setting Vcs-* doesn't make sense in a NMU but because creating an off
On Tue, Mar 11, 2025 at 05:18:49PM -0700, Soren Stoutner wrote:
To a certain degree, promoting official installer images without non-free
firmware next to
installer images with non-free firmware can raise awareness of the problem. To
another
degree, it probably wouldn’t do anything right now e
On Sat, Mar 08, 2025 at 06:58:08PM +0500, Andrey Rakhmatullin wrote:
If you don't trust the vendor, then it makes no difference whether or not new
official firmware/microcode can be uploaded/flashed or not. If you don't trust
the vendor, then the initial microcode that came with y
On Mon, Mar 10, 2025 at 03:41:50PM +0100, Bjørn Mork wrote:
Simon Richter writes:
their questionable choices in buying hardware that ships with non-free
firmware
Is there hardware that ships with free firmware? Seriously.
Yeah, I think that should read "requires", not "ships with". Shippi
On Fri, Mar 07, 2025 at 08:33:50PM +0100, Michael Biebl wrote:
I wonder if we get a reply from the OP or if this was just an attempt
to trigger a flame war. We will see...
Yup.
--
WBR, wRAR
signature.asc
Description: PGP signature
On Mon, Mar 10, 2025 at 08:36:45PM +0900, Simon Richter wrote:
The current state where we have free software drivers for a lot of
hardware is the result of a lot of people investing a lot of time into
creating them.
In the same way, we need to do both: support our current users by
allowing th
On Mon, Mar 10, 2025 at 11:56:28AM +0100, Simon Josefsson wrote:
I still haven't heard arguments why people refuse to use an installer
that comes with non-free firmware, asks whether this firmware should
be used, and if answered "no", none of this non-free firmware ends up
in the installed system
On Sat, Mar 08, 2025 at 02:51:29PM +0100, Johannes Schauer Marin Rodrigues
wrote:
If you don't trust the vendor, then it makes no difference whether or not new
official firmware/microcode can be uploaded/flashed or not. If you don't trust
the vendor, then the initial microcode that came with you
On Fri, Mar 07, 2025 at 11:05:02PM +0530, pan...@disroot.org wrote:
I understand that users need proprietary drivers to run certain
hardware, and Debian should not ignore this reality. That is why I am
not asking Debian to become a fully GNU-endorsed distro like Trisquel,
which rejects all non-
On Thu, Mar 06, 2025 at 02:13:49PM +, Wookey wrote:
Which entry in which release notes will warn that this time
(presumably - was this an upgrade to unstable K.C. or to bookworm, or
something else?) the (pretty old now) eth0 -> 'annoying, unmemorable,
but ordered and unique', renaming will/mi
On Wed, Mar 05, 2025 at 09:32:05PM -0800, James Lu wrote:
If I were to write, say, a Thunderbird extension that forcibly unwraps
text I receive, regardless of whether format=flowed was specified,
what would be the implication?
This (as a mild but easy to get example of pre-formatted text):
Fo
On Tue, Mar 04, 2025 at 05:44:33PM +0100, Andreas Metzler wrote:
On 2025-03-04 Blair Noctis wrote:
On 04/03/2025 01:29, Andreas Metzler wrote:
[...]
> There is another downside to the BTS sending mails to uploaders. - There
> is no simple unsubscribe, it would need a sourceful upload.
I wo
On Tue, Mar 04, 2025 at 07:13:50PM +0800, Blair Noctis wrote:
There is another downside to the BTS sending mails to uploaders. - There
is no simple unsubscribe, it would need a sourceful upload.
I wonder who would bother to add themself to Uploaders of a package,
but then refuse to read bugs re
On Tue, Mar 04, 2025 at 02:12:05PM +0530, Sarbjit Singh Sandhu wrote:
Dear Debian Developers,
I am writing to propose the creation of a new Debian branch that offers a
stable release every year, as opposed to the current 5-year cycle. This
would be particularly beneficial for educational institu
On Thu, Feb 27, 2025 at 06:11:52PM +0900, Charles Plessy wrote:
> > Packages that already install programs to /usr/games, where another
> > package installs a program of the same with different functionality
> > to a different directory on the default PATH, may continue to do so.
>
> H
On Thu, Feb 20, 2025 at 10:05:36AM +0100, Timo Röhling wrote:
> Hello,
>
> I have run into an unexpected quirk of dpkg (I think) and would like to
> solicit some advice on how to handle it.
>
> For better cross building/multi-arch support, I recently moved a bunch of
> files from python3-numpy to
On Tue, Feb 18, 2025 at 09:06:53AM +0900, Charles Plessy wrote:
> Again, given the scale, Debian can not expect that the package
> maintainers are going to contact each upstream and send a patch. We are
> not paid for that.
Yes, Debian only expects that such bugs are forwarded upstream, not
that
On Sun, Feb 02, 2025 at 11:23:33PM -0300, Leo Historias wrote:
> Oh god,I should clarify when i say that...
>
>
> They will drop support for it starting with Trixienot that it is no
> longer supported.
I'm not sure how is it different but this is also not what was planned.
--
WBR, wRAR
s
On Sun, Feb 02, 2025 at 02:18:53PM -0300, Leo Historias wrote:
> As we know, I386 is dropped from Debian Ports starting with Trixie,
As we know it is not, even if by "Debian Ports" here you mean the normal
Debian archive.
--
WBR, wRAR
signature.asc
Description: PGP signature
On Mon, Jan 27, 2025 at 03:22:48PM +0100, PICCA Frederic-Emmanuel wrote:
> Hello, I am trying to use mk-origtargz with a 7zip archive., but I get this
> error message.
>
> $ mk-origtargz ../fiji-linux64.zip
.zip?
> [../fiji-linux64.7z]
What does this mean?
--
WBR, wRAR
signature.asc
Descr
On Sun, Jan 26, 2025 at 01:02:25AM -0600, Steven Robbins wrote:
> > I've come to realise the ITK build has 15 libraries that lintian flags with
> > error library-not-linked-against-libc.
>
> Someone suggested to run ldd -r. Okay, so what does this tell me?
>
> $ ldd -r /lib/x86_64-linux-gnu/libI
On Sun, Jan 26, 2025 at 11:07:12AM +, Ahmad Khalifa wrote:
> > The error description seems straightforward. But how does one solve
> > this? I have to assume that the linker would by default link with the
> > libc (?), so perhaps the linker invocation has options that suppress
> > this? What
On Sat, Jan 25, 2025 at 10:57:26PM -0600, Steven Robbins wrote:
> I've come to realise the ITK build has 15 libraries that lintian flags with
> error library-not-linked-against-libc.
>
> https://lintian.debian.org/tags/library-not-linked-against-libc.html[1]
>
> The error description seems str
On Sat, Jan 25, 2025 at 07:17:52PM +, Tim Woodall wrote:
> I know this is experimental and so breakage is expected but it seems to
> have been like this for a while now so I'm reporting it here in case
> it's been missed.
You may be confused, as perl 5.40.1-1 was only uploaded to experimental
On Sat, Jan 25, 2025 at 03:34:45PM +, Richard Lewis wrote:
> Crypticverse writes:
>
> > Package: wnpp
> > Severity: wishlist
> > Owner: Crypticverse
> > X-Debbugs-Cc: debian-devel@lists.debian.org, crypticvers...@gmail.com
> >
> > * Package name: linux-os-updater
> > Version :
On Mon, Jan 20, 2025 at 05:18:01PM +, Phil Wyett wrote:
> I mainly ran into issue with autopkgtest
Good.
autopkgtest and package building are separate unrelated activities.
--
WBR, wRAR
signature.asc
Description: PGP signature
On Mon, Jan 20, 2025 at 05:10:35PM +, Phil Wyett wrote:
> * A VM with Debian trixie install - standard utilities plus ssh server.
> * sbuild, pbuilder, piuparts and reprotest etc. installed.
> * qemu is not the install.
>
> For --host=arm64 I have to generate an arm64 chroot
No.
> and instal
On Mon, Jan 20, 2025 at 04:35:12PM +, Phil Wyett wrote:
> https://wiki.debian.org/sbuild
>
> https://wiki.debian.org/sbuild#Cross-compiling_packages
>
>
> On the sbuild wiki page in the cross compiling section should we be advising
> users that they need to create a chroot for the {ARCH} the
On Mon, Jan 20, 2025 at 02:02:51AM +1100, Russell Coker wrote:
> How do I specify an override file that works for this? When I have a file
> debian/source/lintian-overrides which works for lintian -c but doesn't work
> for uploading the package.
>
> warzone2100 source: lintian output: 'license-
On Thu, Jan 16, 2025 at 01:54:05PM -0500, Chris Knadle wrote:
> > atomic operations require linking against libatomic — always have. Some
> > architectures inline a few functions, which is how you get away with
> > omitting the library on amd64 most of the time, but this is incorrect.
> >
> > No a
On Thu, Jan 16, 2025 at 08:16:46PM +0100, Johannes Schauer Marin Rodrigues
wrote:
> > atomic operations require linking against libatomic — always have. Some
> > architectures inline a few functions, which is how you get away with
> > omitting
> > the library on amd64 most of the time, but this i
On Thu, Jan 16, 2025 at 01:26:39PM -0500, Chris Knadle wrote:
> Looking at the manpage for dpkg-architecture, the variable I may want to
> conditionally build upon might be DEB_TARGET_ARCH rather than DEB_HOST_ARCH.
No, it should be DEB_HOST_ARCH.
https://gcc.gnu.org/onlinedocs/gccint/Configure-Te
On Thu, Jan 16, 2025 at 09:48:53AM -0500, Chris Knadle wrote:
> I have a situation with mumble where the build is breaking on armel
> architecture. Upstream has identified that this bug is due to the mumble
> "link" plugin containing atomic memory operations. I would like to
> conditionally patch t
On Tue, Jan 14, 2025 at 07:14:09PM -0800, Otto Kekäläinen wrote:
> > The other big category of MRs in the debian namespace was and still
> > is: MRs where the maintainers don't get mails from salsa. If one is
> > active with the project, one can know who is currently around and
> > assign / ping th
On Tue, Jan 14, 2025 at 08:52:39AM +0100, Philip Hands wrote:
> I'd really like to know how it is possible for one to use an LLM to make
> a contribution to a permissively licensed project (e.g. Expat) without
> in effect stealing the code from one's own tribe of Copyleft authors.
>
> Can one even
On Sat, Jan 11, 2025 at 11:25:20AM -0500, M. Zhou wrote:
> Opinion against this post will include something about hallucination.
> In the case LLM write something that does not compile at all, or write
> some non-existent API, a human is intelligent enough to easily notice
> that build failure or l
On Sat, Jan 11, 2025 at 03:38:10PM +, Ahmad Khalifa wrote:
> > Write on Google "Debian create new package" and first result: https://
> > wiki.debian.org/HowToPackageForDebian
> >
> > It points to various parts but mainly the more probable start point
> > seems https://wiki.debian.org/Packagin
On Sat, Jan 11, 2025 at 01:49:33PM +0100, Fabio Fantoni wrote:
> I don't know if I've managed to explain well what I mean, but from what I've
> seen over the years, most of the people I've seen trying to approach
> packaging have had difficulty finding documentation and help (even on
> mentors, alt
On Tue, Jan 07, 2025 at 12:46:46PM +0100, Julien Plissonneau Duquène wrote:
> > > This change basically adds the recommendation to use "upstreamvcs"
> > > as the
> > > name of the "git remote" to access the upstream repository and it also
> > Like many others, this looks like a gratuitous change fo
On Sun, Dec 29, 2024 at 01:08:49PM +0100, Ansgar 🐱 wrote:
> I'm wondering how we can clean up suites like experimental and
> unstable. They tend to slowly accumulate cruft that nobody cleans up,
> including no longer installable packages.
>
> As a very simple start, I would like to remove packages
On Sun, Dec 22, 2024 at 07:26:15AM +0100, Andreas Metzler wrote:
> >> Uploads to the archive are not irreversible. You can just as well
> >> upload a new version reverting whatever was done.
>
> >> Please everybody stop treating the archive as the holy thing that
> >> only blessed maintainers can
On Thu, Dec 19, 2024 at 04:58:06PM +0100, Samuel Thibault wrote:
> > And it is actively harmful as if one edits the example configuration to
> > have a useful configuration as dpkg will start annoying admins with
> > "the example configuration has changed; what do you want to do"
> > messages.
>
>
On Thu, Dec 12, 2024 at 09:36:01AM +0100, Jonas Smedegaard wrote:
> > > in the
> > > absence of a debian/dont_touch_my_package file, any Debian Developer is
> > > permitted to upload the package.
> >
> > I like this idea.
> >
> > The next step: agree on a "standard" Debian workflow and allow
> >
On Wed, Dec 11, 2024 at 09:27:11AM -0500, Boyuan Yang wrote:
> I would like to add that while self-sustained SMTP facilities is useful, the
> reportbug tool has a strong assumption: it assumes that the bug reporter
> must be using Debian (or one of the Debian derivative, though we know it
> won't w
On Wed, Dec 11, 2024 at 05:50:55PM +0530, Pirate Praveen wrote:
> > > I think a reportbug web based front end that authenticates with salsa
> > > via oauth and sends emails without any email client needing to be
> > > configured will already help.
> >
> > Is it not already the case that you can us
On Tue, Dec 10, 2024 at 08:59:23AM -0500, Boyuan Yang wrote:
> > Here's the default crontabs for debbugs.
> > There do exists an handfull of other instances of debbugs, some might
> > deviate from default settings.
> >
> > Greetings
> >
> > /usr/lib/debbugs/processall >/dev/null
> > 7,22,37,52
On Tue, Dec 10, 2024 at 09:18:06AM +0100, Gard Spreemann wrote:
> Since several people seem to be sharing their experiences with
> (undesirable) challenges in becoming a DD, I thought I'd add a point
> that seemingly hasn't been covered yet:
>
> The BTS is core to Debian. It is e-mail based. While
On Mon, Dec 09, 2024 at 02:02:30PM -0700, Sam Hartman wrote:
> >> It would be great to have a group of DDs that are willing to
> >> regularly check for RFS bugs / mentors.d.n and offer sponsorship
>
> Andrey> Sure. This is true since the beginning of the RFS process,
> Andrey> and
On Sat, Dec 07, 2024 at 02:34:20PM +0100, Andrea Pappacoda wrote:
> Hi all, I've tried catching up with the whole thread, but didn't fully yet.
> So excuse me if this has been asked/answered before.
>
> On Tue Dec 3, 2024 at 3:40 AM CET, Sean Whitton wrote:
> > Then just make one: 'git deborig'.
>
On Wed, Dec 04, 2024 at 06:08:00PM +0100, Andreas Tille wrote:
> I wonder if we should reconsider the default assumption of package
> ownership. Instead, we could introduce a file, such as
> debian/dont_touch_my_package (or a similarly named file), where
> maintainers can document their reasons for
On Wed, Dec 04, 2024 at 03:30:23PM -0800, Xiyue Deng wrote:
> It would be great to have a group of DDs that are willing to regularly
> check for RFS bugs / mentors.d.n and offer sponsorship
Sure. This is true since the beginning of the RFS process, and as nothing
stops people from doing this, but
On Wed, Dec 04, 2024 at 08:03:49PM +0100, Simon Josefsson wrote:
> I suspect the RFS process would be more successful in finding a sponsor
> if the requests went to debian-devel rather than another opt-in mailing
> list. I rarely go looking for more work to do by viewing
>
> https://bugs.debian.o
On Wed, Dec 04, 2024 at 10:39:52AM -0700, Soren Stoutner wrote:
> I have directed several RFS (Request For Sponsor) towards appropriate teams,
> when then exist. However, my personal experience is that the majority of RFS
> that come into Debian Mentors do not fit neatly into any existing team.
On Wed, Dec 04, 2024 at 04:53:07PM +0100, Robert Chéramy wrote:
> 1) Documentation
> There was a lot of reading involved (no problem here - it is great to have a
> detailed documentation) but it was very confusing that there were different
> guides addressing the same things:
>
> Debian Developper
On Tue, Dec 03, 2024 at 09:56:44AM +0200, Martin-Éric Racine wrote:
> > Would I bother to go through NM now if the process were more
> > simplified/streamlined? Maybe, but probably not. As you noted,
> > priorities matter and it's entirely possible to be involved in
> > Debian without that (dependi
On Tue, Dec 03, 2024 at 10:40:03AM +0800, Sean Whitton wrote:
> >> > One possible rebuttal to this is "gbp needs to do the right thing then".
> >> > Currently gbp by default generates a broken tarball, which is also a
> >> > source of confusion for many.
> >>
> >> Do you have a bug report number?
>
On Mon, Dec 02, 2024 at 06:46:52AM -0600, rhys wrote:
> 1. First, root and ordinary users will not be able to use commands in
> each
> other's directories, which will greatly increase their security
> >>>
> >>> (typical level of argumentation)
[...]
> It's quite simple, and has n
On Mon, Dec 02, 2024 at 11:50:17AM +, Greg Stark wrote:
> > > This is not correct. Whether any of /usr/bin,/usr/sbin,/bin or /sbin
> > > share a partition or not has no relationship to whether a user can
> > > invoke a command, or whether that path is searched for unqualified
> > > command name
On Mon, Dec 02, 2024 at 12:30:52PM +0300, Hakan Bayındır wrote:
> >> 1. First, root and ordinary users will not be able to use commands in each
> >> other's directories, which will greatly increase their security
> >
> > (typical level of argumentation)
> >
> The ability to isolate users from com
On Mon, Dec 02, 2024 at 09:38:28AM +0800, kindusmith wrote:
> 1. First, root and ordinary users will not be able to use commands in each
> other's directories, which will greatly increase their security
(typical level of argumentation)
--
WBR, wRAR
signature.asc
Description: PGP signature
On Thu, Nov 28, 2024 at 07:33:27PM +0530, Pirate Praveen wrote:
> 2024, നവം 28 5:46:47 PM Andrey Rakhmatullin :
> >
> >> Same works with
> >>
> >> pravi@mahishi2:/tmp/node-cacache$ gbp export-orig --pristine-tar
> >
> > Not sure what does this imply.
On Thu, Nov 28, 2024 at 05:37:41PM +0530, Pirate Praveen wrote:
> This can now be reproduced with node-cacache
>
> pravi@mahishi2:/tmp$ gbp clone --pristine-tar
> g...@salsa.debian.org:js-team/node-cacache.git
> gbp:info: Cloning from 'g...@salsa.debian.org:js-team/node-cacache.git'
> pravi@mahish
On Thu, Nov 28, 2024 at 10:49:09AM +0100, gregor herrmann wrote:
> > > As person B I don't want to go hunting for a tarball and place it in
> > > the right place, I want gbp to re-create it from the pristine-tar
> > > branch.
> > Who cares? gbp export-orig takes care of it, unless you need to actua
On Thu, Nov 28, 2024 at 09:41:53AM +0100, Marco d'Itri wrote:
> On Nov 27, gregor herrmann wrote:
>
> > As person B I don't want to go hunting for a tarball and place it in
> > the right place, I want gbp to re-create it from the pristine-tar
> > branch.
> Who cares? gbp export-orig takes care of
On Tue, Nov 26, 2024 at 08:30:31PM -0800, Otto Kekäläinen wrote:
> > > > One possible rebuttal to this is "gbp needs to do the right thing then".
> > > > Currently gbp by default generates a broken tarball, which is also a
> > > > source of confusion for many.
> > >
> > > Do you have a bug report n
On Tue, Nov 26, 2024 at 08:49:44PM +0100, Simon Josefsson wrote:
> >> > >> > Yes, as they don't enable pristine-tar
> >> > >>
> >> > >> Is pristine-tar still valuable these days?
> >> > >
> >> > > Unfortunately yes. AFAIK the two options for fixing this that are
> >> > > usually proposed are:
> >>
On Tue, Nov 26, 2024 at 12:21:55PM -0700, Soren Stoutner wrote:
> > > # Specify the distribution, -d
> > > $distribution = 'unstable';
> >
> > Setting this will override the Distribution of the .changes file created by
> > sbuild with "unstable", ignoring what your package has set. Are you sure yo
On Tue, Nov 26, 2024 at 06:53:01PM +0100, Mechtilde Stehmann wrote:
> > One possible rebuttal to this is "gbp needs to do the right thing then".
> > Currently gbp by default generates a broken tarball, which is also a
> > source of confusion for many.
>
> Do you have a bug report number?
No.
I've
On Tue, Nov 26, 2024 at 06:54:18PM +0100, Chris Hofstaedtler wrote:
> > >> > Yes, as they don't enable pristine-tar
> > >>
> > >> Is pristine-tar still valuable these days?
> > >
> > > Unfortunately yes. AFAIK the two options for fixing this that are
> > > usually proposed are:
> > >
> > > 1) trea
On Tue, Nov 26, 2024 at 04:27:37PM +0100, Simon Josefsson wrote:
> >> > Yes, as they don't enable pristine-tar
> >>
> >> Is pristine-tar still valuable these days?
> >
> > Unfortunately yes. AFAIK the two options for fixing this that are
> > usually proposed are:
> >
> > 1) treat it as a problem o
On Tue, Nov 26, 2024 at 11:59:26AM +, Jonathan Dowland wrote:
> > Yes, as they don't enable pristine-tar
>
> Is pristine-tar still valuable these days?
Extremely, unless your workflow requires using something else to get the
upstream tarball from the archive (among other less important
requir
1 - 100 of 282 matches
Mail list logo
