Hi John (2024.10.24_10:44:45_+)
> I am maintaining the package src:kiwi [1] which hasn't been updated in
> Debian for some time since upstream has added tests that only work when
> the package source is installed into the test environment, i.e. available
> through PYTHONPATH.
If it actually ne
Hi Adrian,
* John Paul Adrian Glaubitz
* [2024-10-24 13:11]:
I had to look it up and the mechanism used is called
"entry_points". The kiwi package adds such entry_points and wants
to test them in its testsuite.
Thus, I need to figure out how to make those entry_points visible
from the buil
Hello,
On Fri 25 Oct 2024 at 08:07pm +01, Otto Kekäläinen wrote:
> Thanks for all the comments!
>
> Trying to summarize and expand on the points raised:
>
> Seems this is still the most optimal way to ensure git is correct:
>
>gbp import-dsc --verbose --pristine-tar apt:j4-dmenu-desktop/sid
>
Thanks for all the comments!
Trying to summarize and expand on the points raised:
Seems this is still the most optimal way to ensure git is correct:
gbp import-dsc --verbose --pristine-tar apt:j4-dmenu-desktop/sid
Also, dgit pull can be used to get the latest source automatically, but
unfort
On Fri, Oct 25, 2024 at 12:55:48PM -0400, Noah Meyerhans wrote:
> > > Honestly I'd be happy if we could just establish some expectation that
> > > the NMUer open a merge request for their changes. It can be merged
> > > later without losing anything or requiring additional work. Enforcement
> > >
Hi;
The salvage team largely operates by QAing packages highlighted by BOTD
http://blends.debian.net/botd/botd.html
which means ones with non-wontfix bugs & not uploaded by maintainer for 5 years
& Standards-Version < 4 & no/invalid VCS.
This has a high hit-rate, and I've noticed that many of t
On Fri, Oct 25, 2024 at 03:03:53PM +, Holger Levsen wrote:
> > Honestly I'd be happy if we could just establish some expectation that
> > the NMUer open a merge request for their changes. It can be merged
> > later without losing anything or requiring additional work. Enforcement
> > of this
Package: wnpp
X-Debbugs-Cc: debian-devel@lists.debian.org,
pkg-systemd-maintain...@lists.alioth.debian.org
Owner: Christian Göttsche
Severity: wishlist
* Package name: systemd-netlogd
Version : 1.4.2
Upstream Contact: Susant Sahani
* URL : https://github.com/systemd/s
Package: wnpp
Severity: wishlist
Owner: Jakob Haufe
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: openterface-qt
Version : TBA, still in early development
Upstream Contact: TechxArtisan Studio
* URL : https://github.com/TechxArtisanStudio/Openterface_QT/
On Fri, Oct 25, 2024 at 10:06:56AM -0400, Noah Meyerhans wrote:
> Honestly I'd be happy if we could just establish some expectation that
> the NMUer open a merge request for their changes. It can be merged
> later without losing anything or requiring additional work. Enforcement
> of this expecta
On Fri, Oct 25, 2024 at 10:06:56AM -0400, Noah Meyerhans wrote:
> > I would very much prefer if it was possible in Debian to not allow
> > the archive to get out of sync with packaging git repo (for example
> > when it lives under salsa.debian.org/debian which uploaders should have
> > access to al
Package: wnpp
X-Debbugs-Cc: debian-devel@lists.debian.org, Debian Python Team
Owner: Roland Mas
Severity: wishlist
* Package name: python-jsonlines
Version : 4.0.0
Upstream Contact: Wouter Bolsterlee
* URL : https://github.com/wbolster/jsonlines
* License :
Hello,
On Thu 24 Oct 2024 at 09:36pm +01, Otto Kekäläinen wrote:
> Hi,
>
> I occasionally run into the situation that a package has been NMU'd or
> otherwise updated directly into the Debian repositories,
> bypassing/ignoring that a packaging git repository existed. I was
> wondering what techniq
On Fri, Oct 25, 2024 at 08:45:16AM +0200, Andreas Henriksson wrote:
> I would very much prefer if it was possible in Debian to not allow
> the archive to get out of sync with packaging git repo (for example
> when it lives under salsa.debian.org/debian which uploaders should have
> access to alread
Hello,
On Fri 25 Oct 2024 at 12:37pm +05, Andrey Rakhmatullin wrote:
> Not sure what's the logic here, but I feel like what you thought about may
> require some "tag to upload" solution not to be just implemented but also
> mandated, which won't happen.
We do intend to automatically import all u
Hello,
On Tue 15 Oct 2024 at 09:03am +02, Joachim Zobel wrote:
> Hi.
>
> DEP-14 states under "About repacked upstream sources" that files that
> are removed from repacked sources should not be in the upstream
> branches.
>
> This does however create modify/delete conflicts when upstream modifies
Package: wnpp
X-Debbugs-Cc: debian-devel@lists.debian.org, Debian Python Team
Owner: Roland Mas
Severity: wishlist
* Package name: python-maggma
Version : 0.70.0
Upstream Contact: The Materials Project
* URL : https://github.com/materialsproject/maggma/
* License
Package: wnpp
X-Debbugs-Cc: debian-devel@lists.debian.org, Debian Python Team
Owner: Roland Mas
Severity: wishlist
* Package name: python-pydash
Version : 8.0.3
Upstream Contact: Derrick Gilland
* URL : https://github.com/dgilland/pydash
* License : MIT
Pr
>
> "the archive is the truth"
> "git is the truth"
Maybe you can rephrase it to "the archive is the present and git is the
future". For instance if a NMU is obsoleted by a new upstream release,
you can ignore the NMU and continue from your latest upload.
Have a nice day,
Charles
On Fri, Oct 25, 2024 at 11:22:25AM +0100, Peter B wrote:
> > I occasionally run into the situation that a package has been NMU'd or
> > otherwise updated directly into the Debian repositories,
> > bypassing/ignoring that a packaging git repository existed.
>
> Hi Otto,
>
> Are any of these packa
Hi,
Each team has their own policy in place. Some teams just want you to request
access if you want to work on a team package (eg: go team), but for some teams
the membership is granted only after confirming they've read and accepted the
team policy (eg: python team), regardless of whether they
On 25/10/2024 11:49, Jonas Smedegaard wrote:
If my understanding is correct, then it sounds wrong for DDs to be
granted access to all Salsa projects.
Hi Jonas,
I was not thinking of all Salsa projects,
but those that represent official packages.
Cheers,
Peter
Quoting Peter B (2024-10-25 12:22:25)
> On 24/10/2024 21:36, Otto Kekäläinen wrote:
> > Hi,
> >
> > I occasionally run into the situation that a package has been NMU'd or
> > otherwise updated directly into the Debian repositories,
> > bypassing/ignoring that a packaging git repository existed.
>
On 24/10/2024 21:36, Otto Kekäläinen wrote:
Hi,
I occasionally run into the situation that a package has been NMU'd or
otherwise updated directly into the Debian repositories,
bypassing/ignoring that a packaging git repository existed.
Hi Otto,
Are any of these packages team maintained?
I un
Hi,
slim came up as Bug of the Day[1] candidate recently. Since that
package seemed of some importance I've answered the bug report about
new upstream version[3]. This triggered the following interesting
response:
Am Thu, Oct 24, 2024 at 11:57:57PM -0500 schrieb Plasma (David Paul):
> On Thu, 2
Hello: I've been trying to use Debian to revive my ASUS C100P Chromebook.
The couple of efforts I've seen like Prawn OS make it hard to enable Wifi
and seem to have gone dormant.
Are there any other possibilities?
I can not claim to be a skilled programmer so am seeking an easily
installed packa
Hi,
I occasionally run into the situation that a package has been NMU'd or
otherwise updated directly into the Debian repositories,
bypassing/ignoring that a packaging git repository existed. I was
wondering what techniques other DDs use to
1) detect that the git packaging repository was bypassed/
* Andreas Henriksson [241025 08:56]:
> > I wanted to check if anyone knows any better techniques or mechanisms
> > than trying to remember to run this command manually before working on
> > a package?
>
> I would very much prefer if it was possible in Debian to not allow
> the archive to get out
On Thu, Oct 24, 2024 at 12:44:45PM +0200, John Paul Adrian Glaubitz wrote:
> (Please CC as I'm not subscribed to debian-devel)
(this is how I realized this is not debian-python@, consider using that
for more relevant coverage)
> I am maintaining the package src:kiwi [1] which hasn't been updated
On Thu, Oct 24, 2024 at 09:36:04PM +0100, Otto Kekäläinen wrote:
> Hi,
>
> I occasionally run into the situation that a package has been NMU'd or
> otherwise updated directly into the Debian repositories,
> bypassing/ignoring that a packaging git repository existed. I was
> wondering what techniqu
On Fri, Oct 25, 2024 at 08:45:16AM +0200, Andreas Henriksson wrote:
> I would very much prefer if it was possible in Debian to not allow
> the archive to get out of sync with packaging git repo (for example
> when it lives under salsa.debian.org/debian which uploaders should have
> access to alread
On 24/10/2024 22:36, Otto Kekäläinen wrote:
Hi,
I occasionally run into the situation that a package has been NMU'd or
otherwise updated directly into the Debian repositories,
bypassing/ignoring that a packaging git repository existed. I was
wondering what techniques other DDs use to
1) detect t
Hi!
...
> > FWIW, I'm happy to administer the service and if Otto also signs up
> > for this with me, we would be two DDs.
> >
> > I think Nicolas has done great job working on this and I've proved I
> > was motivated in helping fixing things in Lintian in the long run.
> >
> > Cheers,
>
> I think
33 matches
Mail list logo
