On Tue, Jun 25, 2024 at 02:02:11PM +0100, Simon McVittie wrote:
> On Tue, 25 Jun 2024 at 10:16:20 +0200, Helmut Grohne wrote:
> > In this work, limitations with --chroot-mode=unshare became apparent and
> > that lead to Johannes, Jochen and me sitting down in Berlin pondering
> > ideas on how to im
Package: wnpp
Severity: wishlist
Owner: Antonio Terceiro <[EMAIL PROTECTED]>
* Package name: libyadis-ruby
Version : 0.3.4
Upstream Author : Brian Ellin, JanRain Inc. <[EMAIL PROTECTED]> and
Eugene Eric Kim, Blue Oxen Associates. <[EMAIL PR
Package: wnpp
Severity: wishlist
Owner: Antonio Terceiro <[EMAIL PROTECTED]>
* Package name: libopenid-ruby
Version : 1.1.4
Upstream Author : Brian Ellin <[EMAIL PROTECTED]>
* URL : http://www.openidenabled.com/openid/libraries/ruby/download
* License
Package: wnpp
Severity: wishlist
Owner: Antonio Terceiro <[EMAIL PROTECTED]>
* Package name: libshoulda-ruby
Version : 1.2.0
Upstream Author : Tammer Saleh, Thoughtbot, Inc.
* URL : http://rubyforge.org/projects/shoulda/
* License : MIT/X
Programmin
Package: wnpp
Severity: wishlist
Owner: Antonio Terceiro <[EMAIL PROTECTED]>
* Package name: libmocha-ruby
Version : 0.5.2
Upstream Author : James Mead <[EMAIL PROTECTED]>
* URL : http://mocha.rubyforge.org/
* License : MIT/X
Programmin
Package: wnpp
Severity: wishlist
Owner: Antonio Terceiro <[EMAIL PROTECTED]>
* Package name: libferret-ruby
Version : 0.11.4
Upstream Author : David Balmain <[EMAIL PROTECTED]>
* URL : http://rubyforge.org/projects/ferret/
* License : MIT/X
Prog
already
Testsuite: foo
and dpkg-source detects the presence of debian/tests/control? Will it
merge `autopkgtest` into the list, or will it replace the existing
value?
--
Antonio Terceiro
signature.asc
Description: Digital signature
n and just trim the “autopkgtest” value?
>
> Does this resolve your concern?
Absolutely.
Thanks,
--
Antonio Terceiro
signature.asc
Description: Digital signature
get the uploaded packages. I remember a discussion about
turning the incoming location into a proper APT repository, but I don't
know in which stage that effort is.
--
Antonio Terceiro
signature.asc
Description: Digital signature
On Tue, Jul 08, 2014 at 05:18:21PM +0200, Ansgar Burchardt wrote:
> Hi,
>
> On 07/08/2014 16:57, Antonio Terceiro wrote:
> > Of course, from there we would also need an APT repository from where to
> > actually get the uploaded packages. I remember a discussion about
>
Package: wnpp
Severity: wishlist
Owner: Antonio Terceiro
* Package name: ruby-spring
Version : 1.1.3
Upstream Author : Jon Leighton
* URL : http://github.com/rails/spring
* License : MIT
Programming Lang: Ruby
Description : Rails application preloader
Package: wnpp
Severity: wishlist
Owner: Antonio Terceiro
* Package name: ruby-exception-notification
Version : 4.0.1
Upstream Author : Jamis Buck
* URL : https://github.com/smartinez87/exception_notification
* License : MIT (Expat)
Programming Lang: Ruby
test runs on ci.debian.net.
--
Antonio Terceiro
signature.asc
Description: Digital signature
On Sun, Aug 17, 2014 at 12:03:44PM -0300, Antonio Terceiro wrote:
> On Sun, Aug 17, 2014 at 12:07:58AM +0200, Ansgar Burchardt wrote:
> > First, the archive used by buildds is now publically accessible in
> > http://incoming.debian.org/debian-buildd/. This location provides ac
ests. Currently, the only defined value is
> > > > autopkgtest.
> > > > +
> > > > +
> > > > +
> > > > + This field is automatically added to Debian source control
> > > > files by
> > >
On Wed, Aug 20, 2014 at 01:38:32PM +0200, Andreas Tille wrote:
> On Tue, Aug 19, 2014 at 07:35:22PM -0300, Antonio Terceiro wrote:
> > >
> > > Anybody Developer who thinks that 1) the Policy is useful and 2) the
> > > Testsuite
> > > field is useful, can
Package: wnpp
Severity: wishlist
Owner: Antonio Terceiro
* Package name: mailman-api
Version : 0.2.3
Upstream Author : Sergio Oliveira
* URL : http://pypi.python.org/pypi/mailman-api/
* License : GPL-2
Programming Lang: Python
Description : REST API
' in case we don't find a
> proper base.cow for it.
This would mean a much more expensive build by default, please don't.
I would rather make plain debuild, or just dpkg-buildpackage, the
default.
--
Antonio Terceiro
signature.asc
Description: Digital signature
gt; set builder=debuild in ~/.gbp.conf
>
> It is no big deal which ever system default is chosen.
I could use the same argument in reverse: if you want to use a full
clean build by default you can also just do that. :)
--
Antonio Terceiro
signature.asc
Description: Digital signature
ded dependencies), plus the need for a
strict dependency on the version of Rails in stable, etc.
--
Antonio Terceiro
signature.asc
Description: Digital signature
metric in the world, that's true, but we don't have a
better one.
--
Antonio Terceiro
signature.asc
Description: Digital signature
(s) to please
consider this alternative so that we can have virtualbox back in main.
--
Antonio Terceiro
signature.asc
Description: Digital signature
SL is inactive upstream and I would't hold my breath
waiting for an upstream release that fixes that.
Any advice on the better course of action in this case?
--
Antonio Terceiro
signature.asc
Description: Digital signature
does not scale. This use case needs to be solved at the
archive level, like emdebian does.
--
Antonio Terceiro
signature.asc
Description: Digital signature
ebian (including this) and
> present your work to mentors [0] and/or the maintainers of the
> package.
Better yet, I think the Javascript packaging team might be a good place
for this:
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
--
Antonio Terceiro
si
mespaces (CPAN/PyPi/Rubygems);
which one gets to use the 'foo' source package name in Debian? First
come first serve won't work.
BTW DEP-5 proposes a explicit field in debian/copyrigh for the upstream
name of packages, so machine discovery of this information should not
be too hard.
--
Antonio Terceiro
signature.asc
Description: Digital signature
Jakub Wilk escreveu isso aí:
> * Antonio Terceiro , 2012-01-25, 10:12:
> >Another argument in favor of using the same name for source and
> >binary packages: suppose there is "libfoo", and independent
> >bindings for Perl, Python and Ruby, all called "foo&qu
Package: wnpp
Severity: wishlist
Owner: Antonio Terceiro
* Package name: ruby2.0
Version : 2.0.0~rc1
Upstream Author : Several
* URL : http://www.ruby-lang.org/
* License : BSD or Ruby
Programming Lang: C, Ruby
Description : Ruby Programming Language
ages.debian.org/rbenv
³ update-alternatives --config ruby
From the Ruby community side the situation is a lot better. You will
even see the occasional "don't you break a stable API" rant within the
Ruby community.
--
Antonio Terceiro
signature.asc
Description: Digital signature
On Fri, Apr 05, 2013 at 12:16:40PM +0200, olivier sallou wrote:
> dh-make-perl indeed for Perl CPAN packages.
>
> dh-make for base packages...
gem2deb for Ruby packages ...
--
Antonio Terceiro
signature.asc
Description: Digital signature
On Thu, Apr 18, 2013 at 04:41:35PM +0200, Matthias Klose wrote:
> - Ruby: Afaik, not yet started on multiarch.
Ruby 2.0 has multiarch support upstream. The Debian packaging is not
finished yet, but it will have multiarch.
I do not plan to multiarch 1.9.
--
Antonio Terceiro
signature.
don't, fine, but you never know.
While I agree with you that there are a lot more we can test, I don't
think it's useless to include tests for stuff we know is working. Even
"trivial" tests have their value with so many moving parts.
--
Antonio Terceiro
signature.asc
Description: Digital signature
Package: wnpp
Severity: wishlist
Owner: Antonio Terceiro
* Package name: debci
Version : 0.4.0
Upstream Author : Antonio Terceiro
* URL : http://ci.debian.net/
* License : GPL-3
Programming Lang: Mostly POSIX Shell. a little bit of (or a rewrite
On Thu, Jan 23, 2014 at 03:17:46PM +0100, Michael Prokop wrote:
> * Antonio Terceiro [Thu Jan 23, 2014 at 10:08:25AM -0300]:
>
> > * Package name: debci
> > Version : 0.4.0
> > Upstream Author : Antonio Terceiro
> > * URL : http:
ere after a reboot. ;-)
--
Antonio Terceiro
signature.asc
Description: Digital signature
Package: wnpp
Severity: wishlist
Owner: Antonio Terceiro
* Package name: vagrant-lxc
Version : 0.8.0-
Upstream Author : Fábio Rehm
* URL : https://github.com/fgrehm/vagrant-lxc
* License : MIT
Programming Lang: Ruby
Description : Linux Containers
only necessary for running the test
> >suite and you don't want to replicate them in the test Depends:.
>
> I advise to never use @builddeps@. It's a great way to shoot
> yourself in the foot. :\
would you ellaborate?
--
Antonio Terceiro
signature.asc
Description: Digital signature
rubygems-integration/1.8; apt-file search
/usr/share/rubygems-integration/1.9.1) | cut -d : -f 1 | sort -u | wc -l
300
--
Antonio Terceiro
signature.asc
Description: Digital signature
Ruby 1.8 needs only gcc-4.6 ... which needs
patchutils. So we got ourselves a loop there.
I have just committed a change to ruby that AFAICT will actually allow
it to be built against ruby1.8 ( http://deb.li/nZlv ), any ideas on how
to break the loop?
--
Antonio Terceiro
signature.asc
Description: Digital signature
On Fri, May 16, 2014 at 07:43:18AM +0100, Ian Campbell wrote:
> On Thu, 2014-05-15 at 22:49 -0300, Antonio Terceiro wrote:
> > On Thu, May 15, 2014 at 08:20:53PM +0100, Ian Campbell wrote:
> > > On Thu, 2014-05-15 at 02:10 +0100, Wookey wrote:
> > > > Also if an
On Sat, May 17, 2014 at 10:19:26AM +0100, Ian Campbell wrote:
> On Fri, 2014-05-16 at 20:44 -0300, Antonio Terceiro wrote:
> > On Fri, May 16, 2014 at 07:43:18AM +0100, Ian Campbell wrote:
> > > On Thu, 2014-05-15 at 22:49 -0300, Antonio Terceiro wrote:
> > > > On T
Package: wnpp
Severity: wishlist
Owner: Antonio Terceiro
* Package name: ruby-shoulda-matchers
Version : 1.0.0.beta2
Upstream Author : Several authors
* URL : https://github.com/thoughtbot/shoulda-matchers
* License : MIT
Programming Lang: Ruby
Description
Package: wnpp
Severity: wishlist
Owner: Antonio Terceiro
* Package name: ruby-shoulda-context
Version : 1.0.0.beta1
Upstream Author : Several authors
* URL : https://github.com/thoughtbot/shoulda-context
* License : MIT
Programming Lang: Ruby
Description
Package: wnpp
Severity: wishlist
Owner: Antonio Terceiro
* Package name: ruby-pkg-config
Version : 1.1.2~git20110615
Upstream Author : Kouhei Sutou
* URL : https://github.com/rcairo/pkg-config
* License : LGPL-2.1+
Programming Lang: Ruby
Description
Package: wnpp
Severity: wishlist
Owner: Antonio Terceiro
* Package name: ruby-gherkin
Version : 2.4.5
Upstream Author : Mike Sassak, Gregory Hnatiuk, Aslak Hellesøy
* URL : https://github.com/cucumber/gherkin
* License : MIT
Programming Lang: Ruby
Package: wnpp
Severity: wishlist
Owner: Antonio Terceiro
* Package name: cucumber
Version : 1.0.2
Upstream Author : Aslak Hellesøy
* URL : http://cukes.info/
* License : MIT
Programming Lang: Ruby
Description : acceptance testing tool
Cucumber lets
not noticed a single package whose behaviour was changed by the
changes made to the binary packages for grip. So for me it does not seem
to add the same burden as adding new actual architectures would.
--
Antonio Terceiro
http://softwarelivre.org/terceiro
signature.asc
Description: Digital signature
honest, I don't expect Python 2.6 to go away any time soon.
> (For the simple reason that apparently nobody works on making 2.7
> the default...)
Adding more reverse dependencies won't help either.
--
Antonio Terceiro
signature.asc
Description: Digital signature
before the asset pipeline was introduced and
migrating to use it is not always super convenient.
--
Antonio Terceiro
signature.asc
Description: Digital signature
o some example
> > package doing similar thing?
>
> AICCU asks for similar details IIRC. Have a look at that?
You can look at ddclient as well.
--
Antonio Terceiro
signature.asc
Description: Digital signature
Package: wnpp
Severity: wishlist
Owner: Antonio Terceiro
* Package name: ruby-whenever
Version : 0.9.4
Upstream Author : Javan Makhmali
* URL : https://rubygems.org/gems/whenever
* License : Expat
Programming Lang: Ruby
Description : Ruby library to
we will get there eventually. Diaspora¹ is almost done, and
GitLab will follow at some point.
¹ not the existing diaspora-installer package, an actual diaspora
package with its dependency tree properly packaged.
--
Antonio Terceiro
signature.asc
Description: Digital signature
few mornings/afternoons/evenings
during Debconf proper.
--
Antonio Terceiro
signature.asc
Description: Digital signature
Package: wnpp
Severity: wishlist
Owner: Antonio Terceiro
* Package name: chake
Version : 0.6
Upstream Author : Antonio Terceiro
* URL : https://gitlab.com/terceiro/chake
* License : MIT (Expat)
Programming Lang: Ruby
Description : serverless
>
> 0.1.6-2 was tested on 7th May.
>
> http://ci.debian.net/packages/d/django-restricted-resource/unstable/amd64/
> (9th May)
>
> http://ci.debian.net/packages/d/django-testscenarios/unstable/amd64/
> (9th May)
>
> So some tests are being done, just not others.
They all look like timing issues to me, see my response to the first
message of the thread.
--
Antonio Terceiro
signature.asc
Description: Digital signature
t setup, using a
distributed setup with multiple workers and all that fun stuff. Martin Pitt
started that work back during last year, and I continued that for a few months
now. There are still a few details to sort out, but I think we are quite close
to being able to migrate to that.
--
Antonio Terceiro
signature.asc
Description: Digital signature
dsc.
> I never used the entry in debian/control, and I already had "failed"
> tests, and several entries in ci.debian.net (without tests however),
> which means that they at least sometimes look there.
debci uses the Sources file, so yes, the data that comes from the .dsc
--
Antonio Terceiro
signature.asc
Description: Digital signature
Hello,
While I was writing these responses, I was monitoring ci.debian.net, and
it seems I spoke too soon.
On Sun, May 17, 2015 at 12:33:08PM -0300, Antonio Terceiro wrote:
> > Are there currently any problems with debci? Does it really run
> > continiously?
>
> What is h
On Sun, May 17, 2015 at 09:01:06PM +0200, Ole Streicher wrote:
> Dear Antonio,
>
> Antonio Terceiro writes:
> >> Are there currently any problems with debci? Does it really run
> >> continiously?
> >
> > What is happening is that a system that did t
e testbed, and then `apt-get install -f` is called to fix the world.
At the moment what happens is that dpkg-deb blows up at the build
profiles syntax, and autopkgtest aborts. I understand that it does not
make sense for the build profiles syntax to be supported in Depends:, so
I am writing a patch
can still associate the new commit with the old one
as long as you keep the identifier in the commit message. When you
resubmit it knows that that new commit is a new version of the first
one.
I have mostly no idea on how this could be implemented, and I'm also not
sure that these imaginary UI would be the best one, but I hope that
these ideas are useful to start a conversation.
--
Antonio Terceiro
signature.asc
Description: Digital signature
On Tue, Jul 14, 2015 at 05:06:31PM +0100, Ian Jackson wrote:
> Antonio Terceiro writes ("Re: GitHub “pull request ” is proprietary,
> incompatible with Git ‘requ est-pull ’"):
> > I have a few ideas about this. I have used gerrit before, and it
> > provides a really
On Wed, Jul 15, 2015 at 03:25:52PM +0100, Ian Jackson wrote:
> Antonio Terceiro writes ("Re: GitHub “pull request ” is proprietary,
> incompatible with Git ‘req u est-pull ’"):
> > But if there is server side support for anyone to push to some ref in
> > the maintai
a proper diaspora
package in the debian archive (with all its dependencies also in the
archive)?
--
Antonio Terceiro
signature.asc
Description: Digital signature
Package: wnpp
Severity: wishlist
Owner: Antonio Terceiro
* Package name: rerun
Version : 0.10.0
Upstream Author : Alex Chaffee
* URL : https://github.com/alexch/rerun
* License : Expat
Programming Lang: Ruby
Description : tool to launch commands and
he toolchain
> changes to dpkg and debhelper land in sid.
I think that reprocibility is an important issue, and marking
reprocibility bugs as important makes sense to me. That, please also
include a script to test builds for reprocibility in e.g. devscripts
(see #786755) so that maintaine
rules:
https://anonscm.debian.org/cgit/pkg-javascript/jquery.git/tree/debian/rules?h=debian/1.11.3%2bdfsg-3
I had to read the source of the upstream grunt build task, understand
that it uses something called "requirejs", doing some reading on what
requirejs is and how to use it, then extracting the build logic into a
file that could be used with requirejs (which is already packages as
node-reuqirejs) only -- without grunt -- and there we have it.
--
Antonio Terceiro
signature.asc
Description: Digital signature
On Fri, Nov 02, 2018 at 08:58:47AM +, Jonathan Dowland wrote:
> On Sat, Oct 27, 2018 at 09:41:43AM +0200, Wouter Verhelst wrote:
> > On Fri, Oct 26, 2018 at 01:02:57PM -0300, Thadeu Lima de Souza Cascardo
> > wrote:
> > > I meant that we would say that stable is supported by the security team.
On Wed, Nov 28, 2018 at 02:57:52PM +0100, Guillem Jover wrote:
> Hi!
>
> On Wed, 2018-11-28 at 07:52:08 +0500, Alexander E. Patrakov wrote:
> > Well, the buildd configuration change has been reverted. What worries me now
> > is that there is a risk not yet mitigated, coming from personal systems o
On Wed, Nov 28, 2018 at 07:02:07PM +0100, Bastian Blank wrote:
> On Wed, Nov 28, 2018 at 02:48:32PM -0200, Antonio Terceiro wrote:
> > Would you be willing to also implement
> > Tainted-By: not-built-in-a-chroot
> > ?
>
> What do you want to do with that? Even ou
On Fri, Dec 07, 2018 at 10:45:31AM +0100, Fabiano Fidêncio wrote:
> Howdy!
>
> Firstly, sorry if I'm sending the message to the wrong mailing list.
> If that's the case, please, point me to the right one.
>
> Although the subject says it all, let me explain the background of the
> change so you a
On Fri, Dec 07, 2018 at 08:10:27AM -0200, Antonio Terceiro wrote:
> On Fri, Dec 07, 2018 at 10:45:31AM +0100, Fabiano Fidêncio wrote:
> > Howdy!
> >
> > Firstly, sorry if I'm sending the message to the wrong mailing list.
> > If that's the ca
On Wed, Dec 26, 2018 at 01:04:44PM +0530, Pirate Praveen wrote:
> If it has to be completely separate from -backports, it means some packages
> will need to be maintained twice, even when they meet the criteria for
> backports fully, just because a package in volatile declare a dependency on
> t
On Fri, Mar 08, 2019 at 11:08:54AM +, Mo Zhou wrote:
> Hi folks,
>
> As we know the Debian CI Infrastructure, which runs autopkgtest upon
> relevant package updates to help us improve distribution quality.
> However, it still doesn't support the isolation-machine feature, which
> associates to
On Tue, Jun 25, 2019 at 08:08:22AM +0200, Ansgar wrote:
> Hi,
>
> what do people think about getting rid of current suite names ("stable",
> "testing", "unstable") for most purposes? We already recommend using
> codenames instead as those don't change their meaning when a new release
> happens.
>
On Wed, Jul 10, 2019 at 04:09:11PM +0100, Ian Jackson wrote:
> Sean Whitton writes ("git & Debian packaging sprint report"):
> > Main achievement
> >
> >
> > We designed and implemented a system to make it possible for DDs to
> > upload new versions of packages by simply pushing a
On Wed, Jul 10, 2019 at 05:05:53PM -0400, Sam Hartman wrote:
> I also use systemd.path units for this.
> Since it was Ian asking I didn't really feel that was worth suggesting
> though.
yes, I also though about that but decided to cite prior art anyway. one
can always use inotify to achieve the sa
Hi,
Thanks for the report.
On Wed, Jul 10, 2019 at 09:10:40AM +0100, Sean Whitton wrote:
> Hello,
>
> Over the weekend, Ian Jackson and I met in Cambridge, U.K. to work on
> the design and implementation of tools and processes relating to git &
> Debian packaging.
>
> Main achievement
> ---
On Tue, Aug 27, 2019 at 02:52:01PM -0400, Sam Hartman wrote:
> > "Alf" == Alf Gaida writes:
>
>
> Alf> There are things i really like about PRs or MRs - they can be
> Alf> reviewed, commented, changed without problems and fast.
>
> And as Sean pointed out, it's hard to understand th
On Sat, Jul 29, 2023 at 06:02:26AM +0200, Helmut Grohne wrote:
> Hi,
>
> On Tue, Jul 25, 2023 at 09:37:35PM +0200, Paul Gevers wrote:
> > For ci.d.n, the issue is not money, but the required work to integrate it
> > into the infrastructure. We need volunteers (or pay people to do the work),
> > bu
On Tue, Aug 08, 2023 at 11:35:01AM +0300, Adrian Bunk wrote:
> On Tue, Aug 08, 2023 at 06:46:38AM -, Sune Vuorela wrote:
> > On 2023-08-07, Benjamin Drung wrote:
> > > while working a whole week on fixing failing C/C++ header compilations
> > > for armhf time_t [1], I noticed a common pattern:
On Sat, Dec 16, 2023 at 06:23:46PM +, Paul Gevers wrote:
> Reproducibility migration policy
>
>
> The folks from the Reproducibility Project have come a long way since they
> started working on it 10 years ago, and we believe it's time for the next step
> in De
On Thu, Dec 21, 2023 at 10:41:57AM +0100, Helmut Grohne wrote:
> ## Upgrading using dpkg directly?
>
> We already have quite a number of packages that use Conflicts to prevent
> file loss in upgrades in a very similar way to #1058937 (Ben's
> libnfsidmap1 bug) even in released versions of Debian.
On Tue, Nov 10, 2020 at 06:52:14PM -0500, Calum McConnell wrote:
> On Tue, 2020-11-10 at 10:07 +, Simon McVittie wrote:
> > On Tue, 10 Nov 2020 at 10:45:07 +0100, Johannes Schauer wrote:
> > > I'm confused. We are packaging libraries of language X but then those
> > > packages
> > > will not be
On Mon, Jan 18, 2021 at 02:00:22PM +0100, Pierre-Elliott Bécue wrote:
> Le lundi 18 janvier 2021 à 11:31:35+0100, Lucas Nussbaum a écrit :
> > Hi,
> >
> > On 17/01/21 at 22:00 +0900, Norbert Preining wrote:
> > > On the infrastructure side, you mentioned on #debian-qa that in your
> > > opinion, l
On Tue, Jan 19, 2021 at 12:27:31PM +0100, Raphael Hertzog wrote:
> Hi,
>
> On Mon, 18 Jan 2021, Antonio Terceiro wrote:
> > FWIW, The ci.debian.net infrastructure is mostly independent from
> > autopkgtest, so we could have different types of jobs there. This could
> &g
On Thu, Jan 21, 2021 at 03:10:47PM +0100, Julien Cristau wrote:
> And which of standard or important made most sense (AIUI, standard
> means "installed by default in d-i" and important means "installed by
> default in debootstrap").
wget is already Priority: standard and recommends ca-certificates
On Sun, Feb 14, 2021 at 06:18:12PM -0500, Nick Black wrote:
> I managed to push an update [0] that unexpectedly died in
> autopkgtests [1]. I'm thankful that the tests brought this
> problem to light, and grateful for the bug report--chalk it up
> as a nice win for autopkgtests! I'm now pondering h
Hi,
The Debian CI team would like to encourage and help more maintainers to
add autopkgtest to their packages. To that effect, we now have a
repository called autopkgtest-help on salsa, where we will take help
requests from maintainers working on autopkgtest for their packages:
https://salsa.debi
On Tue, Aug 17, 2021 at 06:51:35AM +, Paul Wise wrote:
> On Mon, Aug 16, 2021 at 1:19 AM Paul Wise wrote:
>
> > 1. the ecosystems I'm talking about include cargo, npm, browser
> > extensions, rubygems, pypi, CPAN etc.
>
> Examples of what current Debian practices are for these ecosystems:
[..
Package: wnpp
Severity: wishlist
Owner: Antonio Terceiro
X-Debbugs-Cc: debian-devel@lists.debian.org, debian-pyt...@lists.debian.org
* Package name: typeshed
Version : n/a
Upstream Author : Several authors
* URL : https://github.com/python/typeshed
* License
On Sun, Oct 24, 2021 at 12:25:23PM +0200, jacobkoch...@gmail.com wrote:
> Hello Stephan,
>
> > Possibly relevant:
> > - Are you using X11 or Wayland?
> Wayland
>
> > - Do you have proprietary graphics drivers installed?
> $ lspci -v | grep -A 10 VGA
> 00:02.0 VGA compatible controller: Intel Corp
Package: wnpp
Severity: wishlist
Owner: Antonio Terceiro
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: ruby-rantly
Version : 2.0.0
Upstream Author : Ana María Martínez Gómez, Howard Yeh, Anthony Bargnesi,
Eric Bischoff
* URL : https://github.com/rantly
On Wed, May 04, 2022 at 01:49:01PM +0200, Mathias Behrle wrote:
> * David Bremner: " Re: Reminder to participate in the Debian Developer's
> Survey" (Wed, 04 May 2022 07:19:34 -0300):
>
> > Utkarsh Gupta writes:
> >
> > > A couple of days back we had invited all the Debian Developers to
> > >
On Tue, Jul 05, 2022 at 06:44:15PM +0200, Timo Röhling wrote:
> On Mon, 23 May 2022 01:58:56 +0200 Andreas Beckmann wrote:
> > Package: faker,ruby-faker
> > Severity: serious
> > Tags: sid bookworm
> > User: trei...@debian.org
> > Usertags: edos-file-overwrite
> > Control: found -1 0.9.3-0.1
> > C
On Sun, Nov 06, 2022 at 01:58:21PM +0900, Hideki Yamane wrote:
> Q4: Will Ruby3.2 go into bookworm?
No.
signature.asc
Description: PGP signature
On Wed, Feb 22, 2023 at 09:24:29AM -0700, Scarlett Moore wrote:
>
> On 2/21/23 15:03, Ryan Kavanagh wrote:
> > On Sun, Feb 19, 2023 at 09:01:56AM -0700, Scarlett Moore wrote:
> > >Description : A tool for glamourous shell scripts
> > >
> > > A tool for glamorous shell scripts. Leverage th
On Wed, Feb 22, 2023 at 03:33:15PM -0700, Sam Hartman wrote:
> >> A tool for glamorous shell scripts. Leverage the power of
> >> Bubbles (https://github.com/charmbracelet/bubbles) and Lip Gloss
> >> (https://github.com/charmbracelet/lipgloss) in your scripts and
> >> aliases wit
On Wed, Oct 02, 2019 at 01:37:58PM +0100, Samuel Henrique wrote:
> On Wed, 2 Oct 2019 at 10:48, Mathias Behrle wrote:
>
> > ...BTW no discussion tool can help in automating
> > separate discussion threads when the topic changes.
> >
>
> They can, I think reddit and hackernews are good at this.
>
On Sun, Nov 17, 2019 at 04:39:46PM +0200, Niko Tyni wrote:
> - for Ruby I only found guidance about application dependencies [2]
> but not module dependencies. The standard library seems to come
> with the interpreter here, so that's not a reason to depend on the
> interpreter package. Still,
1 - 100 of 143 matches
Mail list logo
