Re: DEP18 follow-up: Salsa CI vs Debusine

2024-08-25 Thread Otto Kekäläinen
Hi Helmut! > > Let me suggest that there are more ways to do this. Freexian is putting > > a ton of effort into https://debusine.debian.net. It can do much of the > > same tasks as salsa-ci already (with less flexibility). Extending it to > > act as an upload-proxy that forwards your upload to the

Re: DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?

2024-08-25 Thread Marc Haber
On Sun, 25 Aug 2024 13:31:45 +0200, Fabio Fantoni wrote: >Actually I push keeping "UNRELEASED" even in cases where is near sure to >be ready because I want see salsa CI result and do fixes/improvements if >needed before release, shortly after in major of case I did a release >commit with only f

Re: DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?

2024-08-25 Thread Fabio Fantoni
Il 25/08/2024 08:27, Gioele Barabucci ha scritto: On 25/08/24 01:46, gregor herrmann wrote: Many of the packages are trivial, so updating them (including autopkgtests and blhc and lintian and whatnot) doesn't take longer than 5 minutes. So I can decide to wait for salsa CI for 10 minutes or upd

Re: DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?

2024-08-24 Thread Gioele Barabucci
On 25/08/24 01:46, gregor herrmann wrote: Many of the packages are trivial, so updating them (including autopkgtests and blhc and lintian and whatnot) doesn't take longer than 5 minutes. So I can decide to wait for salsa CI for 10 minutes or update 2 more packages in the same time. (Or try to co

Re: DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?

2024-08-24 Thread gregor herrmann
On Thu, 22 Aug 2024 00:46:09 -0700, Otto Kekäläinen wrote: > Also, I think a 10-minute break is a good thing for the author > themselves. The maintainer should get some fresh air and do the final > review of their changes after a small break to ensure nothing was done > too hastily. That depends

Re: [Debian-salsa-ci] DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?

2024-08-23 Thread Ahmed Siam
On Sat, Aug 24, 2024 at 2:06 AM Ahmed Siam wrote: > On Sat, Aug 24, 2024 at 2:00 AM Ahmed Siam wrote: > > On Sat, Aug 24, 2024 at 1:45 AM Ahmed Siam wrote: > > > Perl pipeline run: > > > - https://salsa.debian.org/ahmedsiam/perl/-/pipelines/719321 > This pipeline run from Nodejs shows a similar

Re: [Debian-salsa-ci] DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?

2024-08-23 Thread Ahmed Siam
On Sat, Aug 24, 2024 at 2:00 AM Ahmed Siam wrote: > > On Sat, Aug 24, 2024 at 1:45 AM Ahmed Siam wrote: > > > > On Sat, Aug 24, 2024 at 1:25 AM Jérémy Lal wrote: > > > A bunch of packages I know (nodejs, receptor to name a few) have salsa CI > > > failures, but no sbuild failures. > > > It woul

Re: [Debian-salsa-ci] DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?

2024-08-23 Thread Ahmed Siam
On Sat, Aug 24, 2024 at 1:45 AM Ahmed Siam wrote: > > On Sat, Aug 24, 2024 at 1:25 AM Jérémy Lal wrote: > > A bunch of packages I know (nodejs, receptor to name a few) have salsa CI > > failures, but no sbuild failures. > > It would be perfect if the build process was exactly the same. > > There

Re: [Debian-salsa-ci] DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?

2024-08-23 Thread Ahmed Siam
On Sat, Aug 24, 2024 at 1:25 AM Jérémy Lal wrote: > A bunch of packages I know (nodejs, receptor to name a few) have salsa CI > failures, but no sbuild failures. > It would be perfect if the build process was exactly the same. There is a work-in-progress MRs about using sbuild for building packa

Re: DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?

2024-08-23 Thread Santiago Ruano Rincón
El 23/08/24 a las 16:00, Theodore Ts'o escribió: > On Fri, Aug 23, 2024 at 03:08:11PM +0200, Marco d'Itri wrote: > > > Salsa CI?) > > The effort needed to do so is so small that the question really should > > be "why should I NOT spend a few seconds enabling Salsa CI?". > > > > > 3) What's the s

Re: DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?

2024-08-23 Thread Marco d'Itri
On Aug 23, Theodore Ts'o wrote: > > salsa update_projects $NAMESPACE/$PROJECT \ > > --jobs yes --ci-config-path recipes/debian.yml@salsa-ci-team/pipeline > > OK, more stupid questions. What is "$NAMESPACE"? Whatever you see after "salsa.debian.org/" in the URL. > And I thought I saw somethin

Re: DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?

2024-08-23 Thread Jérémy Lal
Le mer. 21 août 2024 à 03:36, Otto Kekäläinen a écrit : > Hi! > > In short: > I would very much like to see all top-150 packages run Salsa CI at > least once before being uploaded to unstable. What people think is a > reasonable way to proceed to reach this goal? > > > Background: > We have had s

Re: DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?

2024-08-23 Thread Andrey Rakhmatullin
On Fri, Aug 23, 2024 at 04:00:25PM -0400, Theodore Ts'o wrote: > On Fri, Aug 23, 2024 at 03:08:11PM +0200, Marco d'Itri wrote: > > > Salsa CI?) > > The effort needed to do so is so small that the question really should > > be "why should I NOT spend a few seconds enabling Salsa CI?". > > > > > 3)

Re: [Debian-salsa-ci] DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?

2024-08-23 Thread Otto Kekäläinen
Hi! > And is this web page authoratative? Or just a false search positive? > > https://salsa.debian.org/salsa-ci-team/pipeline#basic-use > > It doesn't mention the "salsa" command at all, but maybe that isn't > the right web page. This goes back to my observation that it would be > helpful i

Re: DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?

2024-08-23 Thread Theodore Ts'o
On Fri, Aug 23, 2024 at 03:08:11PM +0200, Marco d'Itri wrote: > > Salsa CI?) > The effort needed to do so is so small that the question really should > be "why should I NOT spend a few seconds enabling Salsa CI?". > > > 3) What's the simple recipe for enable Salsa CI? > salsa update_projects $NA

Re: DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?

2024-08-23 Thread Marco d'Itri
On Aug 23, Theodore Ts'o wrote: > 1) From a technical respective, what does Salsa CI buy me? Is it just Maybe different and more Debian-specific tests than the one that you are running elsewhere? They should all be documented here: https://salsa.debian.org/salsa-ci-team/pipeline/ . > 2) If I'

Re: DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?

2024-08-23 Thread Theodore Ts'o
On Tue, Aug 20, 2024 at 06:35:52PM -0700, Otto Kekäläinen wrote: > > In short: > I would very much like to see all top-150 packages run Salsa CI at > least once before being uploaded to unstable. What people think is a > reasonable way to proceed to reach this goal? Since I'm the e2fsprogs (one o

Re: DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?

2024-08-22 Thread Bálint Réczey
Hi, Andreas Tille ezt írta (időpont: 2024. aug. 22., Cs, 17:22): > > Am Tue, Aug 20, 2024 at 06:35:52PM -0700 schrieb Otto Kekäläinen: > > ... > > ACK to everything. > > > However, pushing for wider Salsa CI adoption I think makes sense as a > > goal by itself, and I would be keen to hear what pe

Re: DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?

2024-08-22 Thread Andreas Tille
Am Tue, Aug 20, 2024 at 06:35:52PM -0700 schrieb Otto Kekäläinen: > ... ACK to everything. > However, pushing for wider Salsa CI adoption I think makes sense as a > goal by itself, and I would be keen to hear what people think is a > reasonable way to proceed with that? ACK. What about configu

Re: DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?

2024-08-22 Thread Otto Kekäläinen
Hi! > I'd like to rephrase your quest. What you really want is unstable to be > less unstable. Whilst a number of people disagree with that notion, I I don't think anybody disagrees that breaking a core packages and stopping (nearly) all other DDs from doing development for a day or two is accept

Re: DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?

2024-08-21 Thread Helmut Grohne
Hi Otto, On Tue, Aug 20, 2024 at 06:35:52PM -0700, Otto Kekäläinen wrote: > In short: > I would very much like to see all top-150 packages run Salsa CI at > least once before being uploaded to unstable. What people think is a > reasonable way to proceed to reach this goal? > > > Background: > We

Re: DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?

2024-08-21 Thread Andrey Rakhmatullin
On Tue, Aug 20, 2024 at 10:44:30PM -0700, Otto Kekäläinen wrote: > > Something that many developers are probably not aware of is that they > > can enable CI for a repository with no code changes at all and with > > a single command: > > > > salsa update_projects $NAMESPACE/$PROJECT \ > > --jobs

Re: DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?

2024-08-21 Thread Andrey Rakhmatullin
On Tue, Aug 20, 2024 at 06:35:52PM -0700, Otto Kekäläinen wrote: > Hi! > > In short: > I would very much like to see all top-150 packages run Salsa CI at > least once before being uploaded to unstable. What people think is a > reasonable way to proceed to reach this goal? > > > Background: > We

Re: DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?

2024-08-21 Thread Holger Levsen
On Tue, Aug 20, 2024 at 10:44:30PM -0700, Otto Kekäläinen wrote: > > Advertise widely and frequently that there is a pool of people which is > > happy to help investigating the failed CI jobs. > > Then start personally advocating the benefits of CI to the maintainers > > of these packages: I expect

Re: DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?

2024-08-20 Thread Otto Kekäläinen
Hi! > > I would very much like to see all top-150 packages run Salsa CI at > > least once before being uploaded to unstable. What people think is a > > reasonable way to proceed to reach this goal? > Advertise widely and frequently that there is a pool of people which is > happy to help investigat

Re: DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?

2024-08-20 Thread Marco d'Itri
On Aug 21, Otto Kekäläinen wrote: > I would very much like to see all top-150 packages run Salsa CI at > least once before being uploaded to unstable. What people think is a > reasonable way to proceed to reach this goal? Advertise widely and frequently that there is a pool of people which is ha

DEP18 follow-up: What would be the best path to have all top-150 packages use Salsa CI?

2024-08-20 Thread Otto Kekäläinen
Hi! In short: I would very much like to see all top-150 packages run Salsa CI at least once before being uploaded to unstable. What people think is a reasonable way to proceed to reach this goal? Background: We have had several cases recently where an upload to Debian unstable causes widespread

Re: Maven packages in Debian (was Re: Progress in preparing the Bazel Build System for Debian (COVID-19 Biohackathon follow-up))

2020-05-23 Thread Sudip Mukherjee
On Sat, May 23, 2020 at 8:10 PM Thorsten Glaser wrote: > > On Sat, 23 May 2020, Sudip Mukherjee wrote: > > > I have now made a list with package name, the jar files that it > > provides and the list of class that the jar provides. > > This must be scripted/scriptable though… the list for stable is

Re: Maven packages in Debian (was Re: Progress in preparing the Bazel Build System for Debian (COVID-19 Biohackathon follow-up))

2020-05-23 Thread Thorsten Glaser
On Sat, 23 May 2020, Sudip Mukherjee wrote: > I have now made a list with package name, the jar files that it > provides and the list of class that the jar provides. This must be scripted/scriptable though… the list for stable is pretty much fixed, but the one for unstable (which is the relevant

Re: Maven packages in Debian (was Re: Progress in preparing the Bazel Build System for Debian (COVID-19 Biohackathon follow-up))

2020-05-23 Thread Sudip Mukherjee
On Wed, May 13, 2020 at 7:33 PM Thorsten Glaser wrote: > > On Wed, 6 May 2020, Andreas Tille wrote: > > > > Or perhaps we need a webpage or wiki page generated by parsing the > > > Contents file and listing the matching Debian package for each class > > > or, at least, Java package (unless split a

Re: Maven packages in Debian (was Re: Progress in preparing the Bazel Build System for Debian (COVID-19 Biohackathon follow-up))

2020-05-13 Thread Andreas Tille
On Wed, May 13, 2020 at 08:33:07PM +0200, Thorsten Glaser wrote: > > I remember times when such a web page (actually some autogenerated text > > file) existed which was **extremely** helpful. I wished this would be > > back! > > > > > … I just volunteerd, didn’t I? > > Here you are: > > https://

Maven packages in Debian (was Re: Progress in preparing the Bazel Build System for Debian (COVID-19 Biohackathon follow-up))

2020-05-13 Thread Thorsten Glaser
On Wed, 6 May 2020, Andreas Tille wrote: > > Or perhaps we need a webpage or wiki page generated by parsing the > > Contents file and listing the matching Debian package for each class > > or, at least, Java package (unless split across multiple packages)… > > I remember times when such a web page

Re: Progress in preparing the Bazel Build System for Debian (COVID-19 Biohackathon follow-up)

2020-05-06 Thread Andreas Tille
Hi Thorsten, On Wed, May 06, 2020 at 05:15:04PM +0200, Thorsten Glaser wrote: > > Provides or something to make it clear? I saw changes to packages adding > > Or perhaps we need a webpage or wiki page generated by parsing the > Contents file and listing the matching Debian package for each class

Re: Progress in preparing the Bazel Build System for Debian (COVID-19 Biohackathon follow-up)

2020-05-06 Thread Sudip Mukherjee
On Wed, May 6, 2020 at 6:43 AM Olek Wojnar wrote: > > Fellow Developers, Maintainers, and Contributors, > > This is a quick update on recent progress with packaging the Bazel Build > System [1] for Debian. My involvement grew out of an urgent need for > TensorFlow that was identified during the re

Re: Progress in preparing the Bazel Build System for Debian (COVID-19 Biohackathon follow-up)

2020-05-06 Thread Olek Wojnar
On Wed, May 6, 2020 at 11:23 AM Thorsten Glaser wrote: > Or perhaps we need a webpage or wiki page generated by parsing the > Contents file and listing the matching Debian package for each class > or, at least, Java package (unless split across multiple packages)… > > … > > … > > … I just volunte

Re: Progress in preparing the Bazel Build System for Debian (COVID-19 Biohackathon follow-up)

2020-05-06 Thread Olek Wojnar
Hi Emmanuel, On Wed, May 6, 2020 at 10:03 AM Emmanuel Bourg wrote: > > You can remove javax-annotation from the list, it's already packaged as > libgeronimo-annotation-1.3-spec-java. Also error-prone and > checker-framework provide annotations that are not required at runtime, > patching them ou

Re: Progress in preparing the Bazel Build System for Debian (COVID-19 Biohackathon follow-up)

2020-05-06 Thread Thorsten Glaser
On Wed, 6 May 2020, Andrej Shadura wrote: > I wonder could we improve the package description and maybe add some YES please, me either. Why even Geronimo, why not Jakarta’s, which is the most latest? > Provides or something to make it clear? I saw changes to packages adding Or perhaps we need a

Re: Progress in preparing the Bazel Build System for Debian (COVID-19 Biohackathon follow-up)

2020-05-06 Thread Emmanuel Bourg
Hi Olek, Le 06/05/2020 à 07:42, Olek Wojnar a écrit : > We have more information available, including links to RFP bugs, on our > Workplan wiki [3]. If you have Java experience and are willing to assist > in this effort, even packaging one of these would be a great help. If > you also want to hel

Progress in preparing the Bazel Build System for Debian (COVID-19 Biohackathon follow-up)

2020-05-05 Thread Olek Wojnar
Fellow Developers, Maintainers, and Contributors, This is a quick update on recent progress with packaging the Bazel Build System [1] for Debian. My involvement grew out of an urgent need for TensorFlow that was identified during the recent COVID-19 Biohackathon [2]. Upstream has been very support

follow up

2018-11-18 Thread Ryan Martyn
Hi there, Is your business hiring? If so, you can post your job openings to 100+ job sites at no cost for two weeks (valid until 5pm today). Get started with your two-week trial here if you're interested. It's pretty straightforward, but please let me know if you have any questions. If you're

Follow Up To IBM WebSphere or Apache Tomcat or Oracle WebLogic or IIS 7.5 Users List

2018-02-23 Thread Jamie Messer
Good Day, I hope this email finds you well. I am writing to you in regards to our recent list release, and check if you would be interested in acquiring recently verified Top IBM WebSphere or Apache Tomcat or Oracle WebLogic or IIS 7.5 Users List. Every contact from this database has completed

Follow-up: Alioth: the future of mailing lists

2017-09-17 Thread Alex Muntada
Alexander Wirt: > - Distribution lists for use in the Maintainer: field. We suggest > that, with maybe some extra code, this use-case could be well served > by the tracker.debian.org service for almost all purposes. For > larger teams, such as the Debian Perl Group, a list on lists.debian.

A quick follow up to Pivotal users list

2017-03-30 Thread mary . hughes
Hi, A Quick Follow up to you that if you are interested in *Pivotal users list* which can help you to grow up your business campaigns? * Specialties*: big data, cloud computing, hadoop, analytics, software, open source software, containerization, private cloud, data science, cloud foundry

Re: libstdc++ follow-up transitions

2015-08-27 Thread Julien Cristau
On Tue, Aug 25, 2015 at 08:48:54 +0100, Simon McVittie wrote: > Release team, here are some suggestions for binNMUs and other > wanna-build interactions: > > Fixes for some earlier failures, and version skews caused by > maintainer-built binaries not being discarded: > > # retry failed build wit

Re: libstdc++ follow-up transitions

2015-08-25 Thread Simon McVittie
On 17/08/15 11:07, Matthias Klose wrote: > There is now another test rebuild [2] done > with an augmented dh_makeshlibs printing cxx11 symbols in libraries [3]. No > new > bug reports were filed yet. ... > [2] https://people.debian.org/~doko/logs/gcc5-20150813/archive-gcc-08-13-2015/ > [3] deb ht

Re: libstdc++ follow-up transitions

2015-08-24 Thread Matthias Klose
On 08/21/2015 01:12 PM, Simon McVittie wrote: > On 18/08/15 00:37, Steve Langasek wrote: >> On Mon, Aug 17, 2015 at 01:46:16PM +0100, Simon McVittie wrote: >>> Having done more rebuilds in Ubuntu, it would be great if you could >>> publish a complete list of the transitions you believe to be necess

Re: libstdc++ follow-up transitions

2015-08-21 Thread Rene Engelhard
Hi, On Fri, Aug 21, 2015 at 12:12:40PM +0100, Simon McVittie wrote: > hunspell is one notable exception, if it does indeed need renaming (I > haven't verified) It was already bin-NMUed without renaming 16d ago. That said, a testbuild of LO with non-transitioned libs did NOT give me a build failur

Re: libstdc++ follow-up transitions

2015-08-21 Thread Simon McVittie
On 18/08/15 00:37, Steve Langasek wrote: > On Mon, Aug 17, 2015 at 01:46:16PM +0100, Simon McVittie wrote: >> Having done more rebuilds in Ubuntu, it would be great if you could >> publish a complete list of the transitions you believe to be necessary > > Here's the count of source packages in Ubu

Re: libstdc++ follow-up transitions

2015-08-17 Thread Steve Langasek
Hi Simon, On Mon, Aug 17, 2015 at 01:46:16PM +0100, Simon McVittie wrote: > I notice that Ubuntu has gone ahead with a lot of library renames. Did > the Ubuntu developers doing these uploads test the results, or did you > just "upload and hope"? One reason I have held back from doing more NMUs > i

Re: libstdc++ follow-up transitions

2015-08-17 Thread Julien Cristau
On Mon, Aug 17, 2015 at 13:46:16 +0100, Simon McVittie wrote: > I notice that Ubuntu has gone ahead with a lot of library renames. Did > the Ubuntu developers doing these uploads test the results, or did you > just "upload and hope"? One reason I have held back from doing more NMUs > is that for t

Re: libstdc++ follow-up transitions

2015-08-17 Thread Simon McVittie
On 17/08/15 11:07, Matthias Klose wrote: > There seems to be a tendency to avoid transitions, where Debian doesn't have > any > reverse dependencies, or where developers analyze the library API's and come > to > the conclusion that no transition is necessary. I'm not yet sure if this is > the >

Re: libstdc++ follow-up transitions

2015-08-17 Thread Jérémy Lal
2015-08-17 12:47 GMT+02:00 Bastien ROUCARIES : > On Mon, Aug 17, 2015 at 12:07 PM, Matthias Klose wrote: > > Unstable now has GCC 5 as the default for more than two weeks. The > follow-up > > transitions are in progress, however the list of transitions at [1] is > not &g

Re: libstdc++ follow-up transitions

2015-08-17 Thread Bastien ROUCARIES
On Mon, Aug 17, 2015 at 12:07 PM, Matthias Klose wrote: > Unstable now has GCC 5 as the default for more than two weeks. The follow-up > transitions are in progress, however the list of transitions at [1] is not > exhaustive, because this only covered libraries without dependencies on &g

libstdc++ follow-up transitions

2015-08-17 Thread Matthias Klose
Unstable now has GCC 5 as the default for more than two weeks. The follow-up transitions are in progress, however the list of transitions at [1] is not exhaustive, because this only covered libraries without dependencies on libraries which need a transition. There is now another test rebuild [2

Re: Follow-up transitions for the libstdc++6 ABI changes

2015-08-03 Thread Norbert Preining
On Mon, 03 Aug 2015, Matthias Klose wrote: > - having a vacation and hoping the mess is cleaned up when >you come back. Good luck with that one in the beginning of August - my guess is that there couldn't be worse timed transition if you want devs to be available ;-) Enjoy ... I will be one

Question Regarding A Resource For Prospective Students - Follow-up

2012-10-10 Thread Lillian Clark
Hi there, I wanted to follow up with you and make sure you had received my email I sent a little bit ago regarding my educational resource. I was hoping to get in touch with someone who is responsible for the resources section as my project would be a beneficial addition for others to refer

Partnership Opportunity Follow-Up

2008-08-18 Thread Chuka Ikokwu
Hello Editor-In-Chief of Debian.com, I am writing to follow-up with the Geek Weekly proposal email we sent to you earlier. I wanted to confirm that you received it and to see whether this was something you wanted to consider, or to explore in more detail. As aforementioned, we noticed

Re: Specifying where to follow-up (was: List of packages shipping shell scripts with bashisms + MBF proposal)

2008-01-30 Thread Raphael Geissert
#x27;s no way to set a Reply-To. > > That's a field defined (in RFC 2822) as specifying where posts > intended individually to the author ("replies") should be sent. It > would not be good to have such replies sent instead to a public > mailing list. > > I suspe

Specifying where to follow-up (was: List of packages shipping shell scripts with bashisms + MBF proposal)

2008-01-30 Thread Ben Finney
uthor ("replies") should be sent. It would not be good to have such replies sent instead to a public mailing list. I suspect Raphael instead wants to specify that public follow-up posts (not individual replies) should go to debian-devel. The Mail-Followup-To field is often used for this, bu

Re: Follow-up

1999-01-21 Thread Buddha Buck
> Further versions of this proposal will be posted on the WWW, and the address > of such revisions will be posted to both -devel and -dpkg. Please don't do this. It is not easy for everyone on these lists to access material on the WWW. From past experience with other groups, it really breaks

Follow-up

1999-01-20 Thread fantumn \(Steven Baker\)
Further versions of this proposal will be posted on the WWW, and the address of such revisions will be posted to both -devel and -dpkg.