On Sun, Jul 13, 2025 at 07:14:21AM +0530, Aryan Karamtoth wrote:
I own #1109050 [1] and #1109048 [2]. These both ITPs are python
libraries and I put them into python under section field but I
realised these fit better into science section as these libraries are
a part of SciKit-HEP, whose other
On 13-07-2025 07:14, Aryan Karamtoth wrote:
Hi,
I own #1109050 [1] and #1109048 [2]. These both ITPs are python
libraries and I put them into python under section field but I
realised these fit better into science section as these libraries are
a part of SciKit-HEP, whose other packages are
Hi,
I own #1109050 [1] and #1109048 [2]. These both ITPs are python
libraries and I put them into python under section field but I realised
these fit better into science section as these libraries are a part of
SciKit-HEP, whose other packages are already with Debian Science team.
How do I c
Hello,
On Thu 29 May 2025 at 11:31am +02, Marc Haber wrote:
> On Thu, May 29, 2025 at 10:27:09AM +0100, Sean Whitton wrote:
>>On Wed 28 May 2025 at 10:04pm +02, Marc Haber wrote:
>>> My personal pet peeve is the difference between the source package and the
>>> packaging git repository contents.
oncur.
Greetings
Marc
--
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature | How to make an
Hello,
On Thu 29 May 2025 at 05:26am +02, Joost van Baal-Ilić wrote:
> Isn't this what dgit is supposed to solve?
dgit solves this for people wanting to make local changes and NMUs, yes.
For maintainers, if you want to use patches-applied dgit will be happy
with it but you'll probably want to u
Hello,
On Wed 28 May 2025 at 10:04pm +02, Marc Haber wrote:
> My personal pet peeve is the difference between the source package and the
> packaging git repository contents. Those two especially differ in the state of
> patches: They're applied in the unpacked source package, and not applied in
>
On Thu, May 29, 2025 at 09:54:37AM +0200, Marc Haber wrote:
> On Thu, May 29, 2025 at 09:52:38AM +0200, Joost van Baal-Ilić wrote:
> > A, indeed. Otoh the dgit-people feel a source package should be treated as
> > an
> > intermediate build artifact; not something to be consumed by humans.
>
> Bu
Hi,
On Thu, May 29, 2025 at 09:39:01AM +0200, Marc Haber wrote:
> On Thu, May 29, 2025 at 05:26:31AM +0200, Joost van Baal-Ilić wrote:
> > On Wed, May 28, 2025 at 10:04:01PM +0200, Marc Haber wrote:
> >
> > > My personal pet peeve is the difference between the source package and the
> > > packagi
many| lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Hi,
On Wed, May 28, 2025 at 10:04:01PM +0200, Marc Haber wrote:
>
> thanks for writing the two most comprehensive docs about packaging, git and
> gbp I have read in the last years.
> Impressive work.
+1 !
> On Wed, May 28, 2025 at 06:36:00AM -0700, Otto Kekäläinen wrote:
> > in
> > particular
they represent your
personal opinion and that people who want to delve into alternatives
could read the official docs here, here and here.
in
particular these two:
- https://optimizedbyotto.com/post/debian-packaging-from-git/
I would love this article (or a third one) explaining how to co
Hi,
In my experience many of the discussions about packaging workflows on
this list have many misconceptions, which in turn I think stems from
that our tools are a bit challenging to use, and the documentation is
somewhat lacking. Many tend to struggle to figure out how to do
something, and once
> I'm not sure what that means exactly: are you installing some files
> below /usr/ to then deploy as conffile with ucf below /etc, but in a
> different path than /etc/jupyterhub/config/jupyterhub_config.d/
> ?
I think I forgot to answer this question...
In a previous package the /etc/jupyterhub/
Ok, with rm_conffile I have no more old config file, but the empty directory
are remaining.
I need to do something else in order to remove the now obsolète directory ?
- Le 28 Mai 25, à 10:49, Lorenzo plore...@disroot.org a écrit :
> Hi,
>
> On Wed, 28 May 2025 09:45:37 +0200 (CEST)
> PICCA Frederic-Emmanuel
> wrote:
>
>> Hello, I am updating the jupyterhub package in order to switch to ucf
>> for the configuration part.
>
> I'm not sure what that mea
Hello, I am updating the jupyterhub package in order to switch to ucf for the
configuration part.
when I install the new packages, I get these error message (sorry for the
french).
it means, I can not remove non empty directory
picca@page:~/debian/python-team/packages/jupyterhub$ sudo debi
..
Hi Soren,
I found using
export LC_ALL = C.UTF-8
helped with reproducible builds.
Setting LANG alone seems not sufficient.
Cheers,
Peter
Jeremy,
Thanks for taking the time to dig into this so deeply. I really
appreciate it.
On Friday, April 11, 2025 11:23:06 AM Mountain Standard Time Jeremy
Sowden wrote:
> I am not familiar with Ruby and how it does i18n, but based on a
> quick bit of research, I _suspect_ that there may be a c
On 2025-04-11, at 09:56:28 +0800, Bo YU wrote:
On Fri, Apr 11, 2025 at 7:52 AM Soren Stoutner wrote:
> The Redmine package includes a test run at build time that checks for
> a list of particular response values. The problem is that these
> values are translated. Running the build in a differen
Hi,
On Fri, Apr 11, 2025 at 7:52 AM Soren Stoutner wrote:
>
> The Redmine package includes a test run at build time that checks for
> a list of particular response values. The problem is that these
> values are translated. Running the build in a different language
> causes the test to fail.
>
>
The Redmine package includes a test run at build time that checks for
a list of particular response values. The problem is that these
values are translated. Running the build in a different language
causes the test to fail.
Failure:
ProjectAdminQueryTest#test_project_statuses_values_should_re
Hi Marc,
On 02 Apr 2025 at 08:55:25, Marc Haber wrote:
> On Wed, Apr 02, 2025 at 07:20:32AM +0100, Carles Pina i Estany wrote:
> > I applied some of the suggestions of this thread in my package, thanks
> > very much.
> >
> > On the other hand, while doing something else, I saw a package that had
Hi,
On 05 Apr 2025 at 07:24:27, Carles Pina i Estany wrote:
>
> Hi,
>
> Thanks all for the ideas in this thread about how to notify users that a
> package is ready to be used via systemd service and not used manually.
> Some users of simplemonitor missed it and it compl
Hi,
Thanks all for the ideas in this thread about how to notify users that a
package is ready to be used via systemd service and not used manually.
Some users of simplemonitor missed it and it complicated their lifes.
On 26 Feb 2025 at 10:20:24, Jérémy Lal wrote:
> Le mer. 26 févr. 2025 à 10
;I don't trust Computers. They | Mailadresse im Header
Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Hi,
On 26 Feb 2025 at 09:52:28, lorenzo wrote:
> On Wed, 26 Feb 2025 06:37:43 +0100
> Carles Pina i Estany wrote:
>
> > So I still think that there is room to inform users that a package is
> > systemd ready and the name of the service and I wondered if there is a
> > way to do it.
>
> then yo
Le mer. 26 févr. 2025 à 10:09, lorenzo a écrit :
> On Wed, 26 Feb 2025 06:37:43 +0100
> Carles Pina i Estany wrote:
>
> > So I still think that there is room to inform users that a package is
> > systemd ready and the name of the service and I wondered if there is a
> > way to do it.
>
> then yo
On Wed, 26 Feb 2025 06:37:43 +0100
Carles Pina i Estany wrote:
> So I still think that there is room to inform users that a package is
> systemd ready and the name of the service and I wondered if there is a
> way to do it.
then you can use the package description to mention that the package
inc
tor
> or
> systemctl status simplemonitor
> or
> systemctl status --all
>
> in general I think is reasonable to expect that a user that wants to
> play with services is able to use systemctl to search and query a
> service status.
In the case of simplemonitor package: what I&#
Hi,
On Tue, 25 Feb 2025 06:57:36 +0100
Carles Pina i Estany wrote:
> Unpacking simplemonitor (1.13.0-1) ...
> Setting up simplemonitor (1.13.0-1) ...
> Created symlink
> '/etc/systemd/system/multi-user.target.wants/simplemonitor.service' →
> '/usr/lib/systemd/system/simplemonitor.service'. Proce
On Mon, 24 Feb 2025 13:24:29 +0100
Joost van Baal-Ilić wrote:
> I remember lots of discussion about the question: "should a
> service/daemon get automatically started on first installation?"
> I've just searched in Debian Policy but could not find an answer. It
> this issue still delegated to th
On 25/02/2025 05:57, Carles Pina i Estany wrote:
My question is: how to inform users about systemd integration?
If you mean command line level, then you're probably patching it to
check runtime user then exit?
If USER <> service_user:
print "boo, use systemctl ins
reinventing the wheel). The user tried it that because he didn't
> > realise that simplemonitor was integrated with systemd, the
> > simplemonitor system user, checks on startup, etc.
> >
> > My question is: how to inform users about systemd integration?
>
> If y
ystemd, the
> simplemonitor system user, checks on startup, etc.
>
> My question is: how to inform users about systemd integration?
If your package uses dh_installsystemd to integrate with systemd, that
should be enough.
Lorenzo
>
> As a user, what I do when I wonder about that is &
On Mon, Feb 24, 2025 at 11:48:03AM +0100, Carles Pina i Estany wrote:
>
> Hello,
>
> I've packaged "simplemonitor".
>
> Template: simplemonitor/systemd-info
> Type: note
> _Description: Usage of simplemonitor
> The simplemonitor package integrates with systemd. Set it up in
> /etc/simplem
ystem
> user, checks on startup, etc.
>
> My question is: how to inform users about systemd integration?
NEWS.Debian or nothing.
> But I wonder of any more standard ways to do that, what other packages
> do, etc.
The standard way is to not notify about any non-critical changes.
--
WBR, wRAR
signature.asc
Description: PGP signature
use simplemonitor without systemd (which is possible, but reinventing
the wheel). The user tried it that because he didn't realise that
simplemonitor was integrated with systemd, the simplemonitor system
user, checks on startup, etc.
My question is: how to inform users about systemd integration
David,
On Tuesday, January 21, 2025 10:56:31 AM MST David Kalnischkies wrote:
> Am Mon, Jan 20, 2025 at 02:58:21PM -0700, schrieb Soren Stoutner:
> > if [[ `dpkg-divert --list courier-mta` ]]; then
>
> [[ is a bashism (see checkbashisms from devscripts), so I wonder a bit
> how that worked fo
Am Mon, Jan 20, 2025 at 02:58:21PM -0700, schrieb Soren Stoutner:
> if [[ `dpkg-divert --list courier-mta` ]]; then
[[ is a bashism (see checkbashisms from devscripts), so I wonder a bit
how that worked for you in testing and why lintian and co haven't
screamed at you.
You can see the call fa
On Monday, January 20, 2025 12:25:19 PM MST Soren Stoutner wrote:
> I do appreciate you taking the time to comment. Often nobody makes any
> comments to questions that are asked on the forums, and reading your
comments
> has caused me to think more deeply about dpkg-divert. In this case I
> pers
On Monday, January 20, 2025 4:35:15 AM MST David Kalnischkies wrote:
> Am Sat, Jan 18, 2025 at 11:54:53AM -0700, schrieb Soren Stoutner:
> > courier-mta is the package doing the diverting.
>
> That is what I meant… you are grepping in a list of ALL diversions by
> all packages and everything the l
Am Sat, Jan 18, 2025 at 11:54:53AM -0700, schrieb Soren Stoutner:
> courier-mta is the package doing the diverting.
That is what I meant… you are grepping in a list of ALL diversions by
all packages and everything the local admin has configured. Nothing
defines that the string you match for is not
On Sat, Jan 18, 2025 at 11:54:53AM -0700, Soren Stoutner wrote:
> On Saturday, January 18, 2025 8:41:18 AM MST David Kalnischkies wrote:
> > Am Fri, Jan 17, 2025 at 03:29:39PM -0700, schrieb Soren Stoutner:
> > > if [ dpkg-divert --list | grep courier-mta ]; then
> > Sure, "courier-mta" seems like
On Saturday, January 18, 2025 8:41:18 AM MST David Kalnischkies wrote:
> Hi,
>
> Am Fri, Jan 17, 2025 at 03:29:39PM -0700, schrieb Soren Stoutner:
> > > to test if the diversion is installed you can probably use
> > >
> > > dpkg-divert --list | grep courier-mta
> >
> > Thanks for the pointer. I
Hi,
Am Fri, Jan 17, 2025 at 03:29:39PM -0700, schrieb Soren Stoutner:
> > to test if the diversion is installed you can probably use
> >
> > dpkg-divert --list | grep courier-mta
>
> Thanks for the pointer. I have added the following code:
>
> # Delete the old diversions if they exist, which a
Lorenzo,
On Friday, January 17, 2025 2:07:22 AM MST Lorenzo wrote:
> Upgrade is available in preinstall and postinstall [1] so it needs to be
> one of the two, not sure which one is better, (maybe preinstall? but if
> it fails it goes back the the old version, see dpkg chart)
>
> I'm not sure, bu
I am in the process of salvaging courier. In doing so, I discovered the
package was using dpkg-divert. In discussion with upstream, I found a
solution that doesn’t require dpkg-divert.
https://github.com/svarshavchik/courier/issues/56
My question now is how to safely drop the diversion
On 2024-09-11, at 22:55:32 +0200, Andreas Tille wrote:
> I made some mistake when uploading cal_4.1-1_source.changes to
> DELAYED=10 and tried to delete it from the queue. I was following
> `man dcut` from dput-ng and did:
>
> $ dcut rm --searchdirs -f cal_4.1-1_source.changes
> Uploading comman
Hi,
I made some mistake when uploading cal_4.1-1_source.changes to
DELAYED=10 and tried to delete it from the queue. I was following
`man dcut` from dput-ng and did:
$ dcut rm --searchdirs -f cal_4.1-1_source.changes
Uploading commands file to ftp.upload.debian.org (incoming: /pub/UploadQueue/)
Nicholas D Steeves writes:
> PICCA Frederic-Emmanuel
> writes:
>
>> Hello,
>>
>> I would like to extract from the Debian archive all the files with a given
>> name in my case (meta.yaml)
[snip]
>
> Also, if an exhaustive/complete test isn't required, couldn't some
> criteria for a representati
PICCA Frederic-Emmanuel
writes:
> Hello,
>
> I would like to extract from the Debian archive all the files with a given
> name in my case (meta.yaml)
>
> This is in order to test a sort of autodep8 based on the conda test framwork.
>
> Do we have a script which allows to do this sort of things
Hello,
I would like to extract from the Debian archive all the files with a given name
in my case (meta.yaml)
This is in order to test a sort of autodep8 based on the conda test framwork.
Do we have a script which allows to do this sort of things ?
If not, do we have a DD accessible mach8ine
On Tue, 30 Apr 2024 23:08:42 +0200,
Dimitrios Antoniou wrote:
>Hi,
>
>I have a background in software engineering, albeit limited experience with
>C, C++ and Python. I'm looking to join the Debian community and start
>contributing to the project. I was hoping to get some guidance as to what
>the s
Welcome to Debian!
There are a lot of different ways someone can get started contributing to
Debian. Some of
them are described at:
https://mentors.debian.net/intro-maintainers/[1]
I would recommend reading over the resources on that page. If you have any
questions as
you go, this mailing
Hi,
I have a background in software engineering, albeit limited experience with
C, C++ and Python. I'm looking to join the Debian community and start
contributing to the project. I was hoping to get some guidance as to what
the starting steps would be to someone with my background. Any help is
app
> Are the new tools replacements or additional?
Additional
> then ssh-tools-extra would make sense
That's actually a good suggestion. Thank you
> I don't see why adding a 3rd language
> to the 2 already used makes things 'hard to package'
The scripts are written with minimal dependency
and tes
use you want to supesede the old repository eventually) then
that's up to you as upstream.
> I am not sure how to name the new tools upstream repo
> and therefore the package name.
If the new stuff is intended to be a replacement then ssh-tools2 or
ssh-tools-ng (for 'next generation&#x
stros and OSes).
I am not sure how to name the new tools upstream repo
and therefore the package name.
Currently it's ssh-toolz (with a "z")
since I found examples like **python3-toolz**.
But I also thought about ssh-tools2 sind there is **wget2**.
Any suggestion what the best
Hello Loren,
you can wait till the package cimg-dev is fixed.
you can contact the maintainer if (s)he needs help to fix it.
Kind regards
Mechtilde
Am 03.03.24 um 07:29 schrieb Loren M. Lang:
Hello Mentors,
I was notified that a package of mine is now marked for removal in
testing due to the
Hello Mentors,
I was notified that a package of mine is now marked for removal in
testing due to the time_t change. This seems to be with packages that
are indirect build dependencies. I don't see anything in my own package
that uses time_t or date/time operations. I just want to know what my
resp
Hi,
What's the recommended way to install glib schemas?
Currently I have a .postinst script where I call glib-compile-schemas.
Is this the best way to do it?
Thanks,
Eberhard
OpenPGP_0xE9140597606020D3.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP dig
Dear Mentors,
I have been looking for information on how to handle the submodule of a project
that is not or cannot be packaged for Debian. Say a project I want to package
has the submodule registered at externals/foo/bar. For whatever reason Bar
doesn't exist in the repositories. How
On Wed, 2023-07-12 at 06:49 +, Sune Vuorela wrote:
> Either you need to do a packagename change (and debian specific SONAME
> iwth all that entails; or maybe there is a way to restore the old abi.
> Can you provide a full diff of header,implementation of the relevant
> classes ?
You can also
On 2023-07-11, Pierre Gruet wrote:
> Unfortunately, it turns out fields were added to some class (of which
> size thus increased) in the shared library, so that binaries built
> against a previous version of it now segfault as they are not allocating
> enough space.
Either you need to do a pac
Hi tobi,
Le 11/07/2023 à 16:52, Tobias Frost a écrit :
Hi Pierre,
On Tue, Jul 11, 2023 at 04:10:49PM +0200, Pierre Gruet wrote:
Dear Mentors,
I maintain a package that builds a shared library. I uploaded a new upstream
version of it to Debian, with no removed symbols, no ABI change... Fine.
On Tue, Jul 11, 2023 at 04:10:49PM +0200, Pierre Gruet wrote:
> I maintain a package that builds a shared library. I uploaded a new upstream
> version of it to Debian, with no removed symbols, no ABI change... Fine.
Tobias already explained that there was actually an ABI change, but...
> How shoul
Hi Pierre,
On Tue, Jul 11, 2023 at 04:10:49PM +0200, Pierre Gruet wrote:
> Dear Mentors,
>
> I maintain a package that builds a shared library. I uploaded a new upstream
> version of it to Debian, with no removed symbols, no ABI change... Fine.
> Unfortunately, it turns out fields were added to
Dear Mentors,
I maintain a package that builds a shared library. I uploaded a new
upstream version of it to Debian, with no removed symbols, no ABI
change... Fine.
Unfortunately, it turns out fields were added to some class (of which
size thus increased) in the shared library, so that binari
Hello mentors,
The runit-services package ships "metafiles" that are parsed by
a noawait trigger in runit package; the purpose of the trigger is to
perform actions like (oversimplified) enable/start or stop/disable
a service when the correspondent binary is installed or removed [1].
The problem i
Hi mentor!
I am now in the process of packaging a package, but there are some
unknown issues for me.:(
The upstream project is here: https://gitee.com/wine-ce/wine-ce.
The project needs extra two vendor modules to work. From 'Build From
Source' section, we can see:
```
cd wine
i386_CC="clang -f
On Mon, Jan 30, 2023 at 08:30:26PM +0100, Lorenzo wrote:
> > But overall you need to make sure the SVN repo contains the
> > same files as the published tarball, otherwise the compression
> > difference is not the largest problem you could have.
> right, I should have excluded the .svn directory fr
On Mon, 30 Jan 2023 14:00:48 +0100
Andrey Rakhmatullin wrote:
> >
> > Yes, the latest upstream release (mplayer 1.5) has CVEs and fails to
> > build, so I jumped from 1.4 to 1.5+svn
> Is this a one-time thing? If so, I would just create a tarball
> manually.
I suspect this package may need to al
On Mon, Jan 30, 2023 at 12:53:24PM +0100, Lorenzo wrote:
> > > > > One problem with the tar.gz is that debian/gbp.conf has
> > > > > compression = xz
> > > > So this configuration is wrong ad you need to change it.
> > > I didn't write in my previous message, but the watch file of this
> > > projec
On Sun, 29 Jan 2023 20:09:09 +0100
Andrey Rakhmatullin wrote:
> On Sun, Jan 29, 2023 at 03:45:26PM +0100, Lorenzo wrote:
> > > > One problem with the tar.gz is that debian/gbp.conf has
> > > > compression = xz
> > > So this configuration is wrong ad you need to change it.
> > I didn't write in my
On Sun, Jan 29, 2023 at 03:45:26PM +0100, Lorenzo wrote:
> > > One problem with the tar.gz is that debian/gbp.conf has
> > > compression = xz
> > So this configuration is wrong ad you need to change it.
> I didn't write in my previous message, but the watch file of this
> project looks for a tar.xz
On Sat, 28 Jan 2023 19:24:37 +0100
Andrey Rakhmatullin wrote:
> On Fri, Jan 27, 2023 at 06:02:34PM +0100, Lorenzo wrote:
> > Hello mentors,
> >
> > I want to import a new svn snapshot to update a Debian package,
> > the salsa git repo is already configured for gbp, so I did
> >
> > $ gbp import
On Fri, Jan 27, 2023 at 07:49:21PM +0100, Mechtilde Stehmann wrote:
> Hello Lorenzo,
>
> please use a special gbp.conf.
It would be much more useful if you provided the actual option for this.
(as far as I know it doesn't exist)
Unless you mean something else by "special".
> More information you
On Fri, Jan 27, 2023 at 06:02:34PM +0100, Lorenzo wrote:
> Hello mentors,
>
> I want to import a new svn snapshot to update a Debian package,
> the salsa git repo is already configured for gbp, so I did
>
> $ gbp import-orig -u1.5+svn38408 ../upstreamsvn/mplayer
>
> upstream/mplayer is a directo
Hello Lorenzo,
please use a special gbp.conf.
More information you can get in the manpage of gbp.conf
Regards
MEchtilde
Am 27.01.23 um 18:02 schrieb Lorenzo:
Hello mentors,
I want to import a new svn snapshot to update a Debian package,
the salsa git repo is already configured for gbp, so I
Hello mentors,
I want to import a new svn snapshot to update a Debian package,
the salsa git repo is already configured for gbp, so I did
$ gbp import-orig -u1.5+svn38408 ../upstreamsvn/mplayer
upstream/mplayer is a directory with the unpacked svn checkout.
Gbp creates a ../upstreamsvn/mplayer_1
On Mon, 16 Jan 2023 at 16:06, Andreas Tille wrote:
>
> Hi,
>
> I tried to create a multi-source tarball for scipy in its experimental
> branch[1]. Upstream includes a set of git submodules in its build
> process. I intended to merge all these submodules in a single
> scipy_1.10.0.orig-submodules
I haven’t looked closely at it myself, but qtwebengine-opensource-src
accomplishes
something along these lines using `get-orig-source` in their rules file.
https://salsa.debian.org/qt-kde-team/qt/qtwebengine/-/blob/master/debian/rules[1]
Note that, in their case, you must have the python3-debia
On Mon, Jan 16, 2023 at 05:05:39PM +0100, Andreas Tille wrote:
> Hi,
>
> I tried to create a multi-source tarball for scipy in its experimental
> branch[1]. Upstream includes a set of git submodules in its build
> process. I intended to merge all these submodules in a single
> scipy_1.10.0.orig-
Hi,
I tried to create a multi-source tarball for scipy in its experimental
branch[1]. Upstream includes a set of git submodules in its build
process. I intended to merge all these submodules in a single
scipy_1.10.0.orig-submodules.tar.gz. This tarball is created with a
script[2] which makes su
On 02/01/2023 15:50, Soren Stoutner wrote:
Edit /etc/apt/sources.list to have the following contents:
deb http://deb.debian.org/debian/ testing main contrib non-free
deb-src http://deb.debian.org/debian/ testing main contrib non-free
deb http://deb.debian.org/debian/ unstable main contrib no
Edit /etc/apt/sources.list to have the following contents:
deb http://deb.debian.org/debian/ testing main contrib non-free
deb-src http://deb.debian.org/debian/ testing main contrib non-free
deb http://deb.debian.org/debian/ unstable main contrib non-free
Then run the apt commands mentioned pr
On Mon, Jan 02, 2023 at 07:50:53AM +, Barry wrote:
>
>
> I need to install pyqt qsci to test the built code anyway so…
>
> What is the stanza to get to these debs please?
>
deb http://deb.debian.org/debian/ sid main contrib non-free
deb-src http://deb.debian.org/debian/ sid main contrib no
> On 1 Jan 2023, at 19:39, Mechtilde wrote:
>
> Hello Barry,
>> Am 01.01.23 um 19:42 schrieb Barry Scott:
>>> On 31/12/2022 22:49, Sebastiaan Couwenberg wrote:
>>> On 12/31/22 23:39, Barry wrote:
This is where i need help understanding what i do to get that deb.
>>>
>>> Wait for it to m
Hello Barry,
Am 01.01.23 um 19:42 schrieb Barry Scott:
On 31/12/2022 22:49, Sebastiaan Couwenberg wrote:
On 12/31/22 23:39, Barry wrote:
This is where i need help understanding what i do to get that deb.
Wait for it to migrate to testing. Keep an eye on the excuses:
https://tracker.debian.
On 31/12/2022 22:49, Sebastiaan Couwenberg wrote:
On 12/31/22 23:39, Barry wrote:
This is where i need help understanding what i do to get that deb.
Wait for it to migrate to testing. Keep an eye on the excuses:
https://tracker.debian.org/pkg/qscintilla2
Or install it from unstable in the
On 12/31/22 23:39, Barry wrote:
This is where i need help understanding what i do to get that deb.
Wait for it to migrate to testing. Keep an eye on the excuses:
https://tracker.debian.org/pkg/qscintilla2
Or install it from unstable in the meantime.
Testing migration is complicated by the o
Click on the tracker (the second link). It will tell you why it is not in
testing. Specifically, it tells you this is the problem:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027416
Which has just been fixed.
You can either wait 5 days for it to migrate to testing, or you can edit your
On 31 Dec 2022, at 22:32, Soren Stoutner wrote:
Is this the package you are looking for?https://packages.debian.org/search?keywords=python3-pyqt6.qsciYes that is what i am after. Debian testing does not have it available.This is where i need help understanding what i do to get that d
Is this the package you are looking for?
https://packages.debian.org/search?keywords=python3-pyqt6.qsci
https://tracker.debian.org/pkg/qscintilla2
On December 31, 2022 3:14:43 PM MST, Barry Scott wrote:
>
>On 31/12/2022 17:38, Soren Stoutner wrote:
>>
>> There are already some QScintilla Qt6
On 31/12/2022 17:38, Soren Stoutner wrote:
There are already some QScintilla Qt6 packages. Is one of these the
one you are looking for?
https://packages.debian.org/search?keywords=qscintilla2-qt6
That will be the C binding for Scintilla. Its a build dep of PyQt6.
I need the python3 vers
There are already some QScintilla Qt6 packages. Is one of these the one you
are looking
for?
https://packages.debian.org/search?keywords=qscintilla2-qt6[1]
On Saturday, December 31, 2022 10:30:44 AM MST Barry Scott wrote:
> How do I file a request to get QScintilla packaged for debian testing?
How do I file a request to get QScintilla packaged for debian testing?
There is the python3-pyqt5 package, but the qt6 version is missing.
Barry
On Mon, Sep 12, 2022 at 11:45 PM Paul Wise wrote:
> On Mon, 2022-09-12 at 10:05 -0400, Aaron Boxer wrote:
>
> > My codec project uses SIMD code for x86 and AArch64 architectures.
> > Also, as there are different versions of SIMD i.e. SSE vs AVX vs
> > AVX2, the project uses a library that builds
1 - 100 of 2742 matches
Mail list logo
