Package: python3-poetry
Version: 1.8.2+dfsg-1
Severity: normal
$ sudo apt install -t testing python3-poetry
...
Setting up python3-poetry (1.8.2+dfsg-1)
...
$ poetry run python
No module named 'packaging.metadata'
$ sudo apt install -t testing python3-packaging
...
Setting up python3-packaging
Control: tags -1 moreinfo
Michael and Steve,
I would appreciate some help here.
On Tue, Mar 05, 2024 at 07:33:40AM +, Mark Hindley wrote:
> Control: severity -1 normal
>
> On Tue, Feb 06, 2024 at 05:43:41PM +0000, Mark Hindley wrote:
> > Whilst I am not an expert on
Debian on
their systems and would like to be able to help them get up and runninng.
Note - kernel logs below are with updated FW that I manually installed myself.
Without these I don't have functional graphics of wifi :)
Thanks
Mark
-- Package-specific info:
** Version:
Linux version 6.7.7-amd64
is being raised to specifically track getting the iwlwifi firmware
packages updated
Please let me know how I can help. Happy to do any testing, and I have some
limited experience with packaging from maintaining the firmware-sof-signed
packag>
Thanks
Mark
-- System Information:
Debian Rele
too, but I will do separate
bugs for those
Thanks
Mark
-- System Information:
Debian Release: trixie/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 6.7.7-amd64 (SMP w/22 CPU thre
arly have no recollection of! :-|
Now I look, we have been shipping a variation on it in Devuan since 2020[1].
Mark
[1]
https://git.devuan.org/devuan/cgroupfs-mount/commit/ff91abfaf3a5c5633744ea552084125ec6c68ce5
mount shouldn't be unmounting and remounting
cgroups on upgrade and it needs some dh_installinit magic in d/rules.
Mark
Lorenzo,
I think this issue is sufficiently significant to fix in bookworm. I'll wait
until the fix is well tested first.
Mark
On Wed, May 01, 2024 at 07:10:29PM +0200, Lorenzo wrote:
> > Thanks. Does the attached patch help?
>
> yes, it seems it works
Good.
As small refinement to avoid emitting inappropriate dangling symlink warnings.
Mark
>From 07d2dd72221e961637ea7a9cd2143b6c8a411373 Mon Sep 17 00:
stinstall
> script fails if a sysvinit script in /etc/init.d/ is not executable.
>
> Note that recently debhelper started to chmod -x initscripts when a package is
> removed but not purged, so openrc should deal whit non executebles files under
> /etc/init.d/
Thanks. Do
On Mon, Apr 29, 2024 at 01:11:11AM +0200, Lorenzo Puliti wrote:
> I think this change is worth a NEWS entry, with an example
> that explains how to revert to the previous default.
Sounds a good idea. Thanks.
I'll queue your suggestion for the next upload.
Best wishes,
Mark
led.
$ rmadison -s trixie libssl3 libssl3t64
libssl3t64 | 3.2.1-3 | testing| amd64, arm64, armel, armhf, i386,
mips64el, ppc64el, s390x
libssl3| 3.1.5-1 | testing| armel, armhf
Mark
depends on
libnpth0. However, in trixie, libnpth0 is now provided by libnpth0t64 which
debootstrap doesn't handle.
I suggest changing the test to include gpgv which avoids the t64 transition
whilst providing similar functional coverage.
Patch attached.
Mark
-- System Information:
Debian Release
.
I build a kernel with the patch from #26, which I am running right now. The
problem seems to be gone: borg-backup now runs cleanly. So I assume the mount
is fine with the patch from #26.
I could probably test a kernel if it installs on stable.
Best, Mark.
*** Reporter, please consider answering
Control: reassign -1 lvm2
On Thu, Apr 18, 2024 at 02:24:06PM +0500, Alex Volkov wrote:
> On четверг, 18 апреля 2024 г. 11:38:18 +05 Mark Hindley wrote:
>
> > udevadm: info --cleanup-db
> > "db_persist=" -> "db_persist"
> > requi
> Does this mean that dm mapper should set db_persist in the initramfs?
Or the initramfs generator. AFAICS dracut already does this[1], but I don't
immediately see an equivalent for initramfs-tools.
Are you using initramfs-tools? Does switching to dracut improve the situation?
Mark
[1] ht
; "db_persist"
require explicit "db_persist" to exclude device info from --db-cleanup
It is somewaht opaque, but the relevant commits appear to be in the current
systemd git[1].
Does this mean that dm mapper should set db_persist in the initramfs?
Mark
[1]
https://g
Boian,
On Wed, Apr 17, 2024 at 02:53:08PM +0100, Mark Hindley wrote:
> On Wed, Apr 17, 2024 at 05:25:08PM +0500, Alex Volkov wrote:
> > Now, /etc/init.d/udev for some reason does this in its start clause:
> >
> > ===
> >135 # clean up parts of the database cr
tramfs udev db might have been
or might still be required? Or any unanticipated effects of not doing so?
Thanks
Mark
[1]
https://salsa.debian.org/systemd-team/systemd/-/commit/b56f8637a1e03ac6a45af7820287159df9b506b9
ueued for the next upload.
Mark
I second the original request. I installed yq on my Mac using “brew install
yq”, wrote a script and then deployed it to a Debian machine on which I’d run
“apt install yq". But when I ran the script on the Debian machine I got a
syntax error in the “yq” command. It was then that I realised
close #1068653
Restarting laptop after upgrading to unstable (from stable) worked.
Package: evolution
Version: 3.50.3-1+b1
Severity: grave
I have two accounts (personal and work) and both of them are returning
“Timeout was reached”. I have tried removing the accounts and re-adding
them without success.
personal account is @gmail.com
work account is @EMPLOYER'S-DOMAIN
--
Package: wnpp
Severity: wishlist
Owner: Mark Hindley
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: iwgtk
Version : 0.9
Upstream Contact: Jesse Lentz
* URL : https://github.com/J-Lentz/iwgtk
* License : GPL3+
Programming Lang: C
Description
On Fri, 29 Mar 2024 22:32:23 +0100 Aurelien Jarno
wrote:
> Having dpkg in that list means that such downgrade has to be planned
> carefully.
Might be easier overall to spend that effort on a hard switch to zstd
instead.
mfG mow
erimental:
Indeed. As it was an NMU, I think the etiquette is for the NMUer to fix.
In sid consolekit2 still builds cleanly. Therefore, marking notfound there.
Michael, perhaps you would fix your NMU, or provide a better patch?
Thanks
Mark
Control: severity -1 normal
Preventing autoremoval due to uninstallable dpkg-dev version in testing.
Mark
in favour of a meson subproject.
The pkla-compat tarball also has mocklibc, but that is also patched already.
Getting the multiple layers of quilt and meson patches to work was
unpleasant. So the attached patch may save you some time.
HTH
Mark
[1]
https://github.com/polkit-org/polkit/commit
Control: severity -1 normal
On Tue, Feb 06, 2024 at 05:43:41PM +, Mark Hindley wrote:
> Whilst I am not an expert on this transition or the abi-compliance-checker, a
> quick look at the logs[1] suggests this is a tool configuration issue and
> src:consolekit2 may not require t64
Sent message type=signal sender=n/a
destination=n/a
path=/org/freedesktop/systemd1/unit/run_2drd2fa855982314217b00729153ec6dd8b_2eservice
interface=org.freedesktop.DBus.Properties member=PropertiesChanged
cookie=6130 reply_cookie=0 signature=sa{sv}as error-name=n/a
error-message=n/a
Mark
--
Mark Gardner
--
Package: davmail-server
Version: 6.0.1.3390-7
Severity: wishlist
X-Debbugs-Cc: none, m...@vt.edu
Dear Maintainer,
The issue is repeatable with a fresh install of a Debian 12 LXC container:
$ lxc launch images:debian/12 davmail-bug
$ lxc exec davmail-bug bash
# cat /etc/os-release
Package: src:linux
Followup-For: Bug #1063656
X-Debbugs-Cc: deb...@mlkenterprises.com
Dear Maintainer,
* What led up to the situation?
When upgrading from kernel 6.1.0-17-amd64 to 6.1.0-18-amd64 I get the
error message of incompatible module nivida.ko
* What exactly did you do
Control: tags -1 upstream
Jakob,
Many thanks for this.
Jesse,
What are your thoughts? Is this something you can improve or address upstream?
Thanks
Mark
Whilst I am not an expert on this transition or the abi-compliance-checker, a
quick look at the logs[1] suggests this is a tool configuration issue and
src:consolekit2 may not require t64 migration.
Can you clarify?
Thanks
Mark
[1]
https://adrien.dcln.fr/misc/armhf-time_t/2024-02-03T09:18:00
appears to be broken and all the experimental builds FTBFS[1].
In addition, the bug severity is triggering autoremoval[2]
That seems a sub-optimal combination. I am minded to reduce the bug
severity. But I will wait for your response if you have a better suggestion.
Thanks
Mark
[1]
https://bui
Control: tags -1 patch
On Mon, Jan 22, 2024 at 02:37:39PM -0700, Sam Hartman wrote:
> >>>>> "Mark" == Mark Hindley writes:
>
> Mark> Can you confirm?
>
> I agree that should work.
> I have enough confidence and am busy enough today that I
ght is that restart should really be 'no' if it is a new
sysvinit-core installation. The attached patch fixes sysvinit-core installation
within a podman container for me. I need to do more testing to check that it
doesn't cause breakage elsewhere.
Can you confirm?
Thanks
Mark
>From a14a542cf08db3ef5
th upgrades? Or is there another detail in
the dependency chain I have missed?
Mark
[1] https://bugs.debian.org/1052064
[2] Upstream has still not released 254
[3]
https://git.devuan.org/devuan/elogind/src/branch/debian/debian/patches/Use-libsystemd0-compatible-cgroups-layout.patch
Package: pdudaemon
Version: 0.0.8.58.g597052b-1
Severity: serious
Attempting to use pdudaemon without python3-aiohttp installed results in
a traceback:
# pdudaemon
Traceback (most recent call last):
File "/usr/sbin/pdudaemon", line 33, in
sys.exit(load_entry_point('pdudaemon==0.1',
This seems to be the same issue as this one upstream:
https://gitlab.gnome.org/GNOME/mutter/-/issues/2815
The latest debian update made wayland work for me again, and I found the
accessibility zoom feature was somehow active for my greeter session, some
curious kids may have clicked on things.
Please refer to this path traversal vulnerability as CVE-2023-7207.
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-7207
On Wed, Dec 20, 2023 at 10:14:44PM +0100, Jérémy Lal wrote:
> BURP wrong zlib version check in the failing test - this could be NMUed
> DOLFIN has a single test failure, that is odd and unrelated as well - this
> could be NMUed
For non-technical reasons I can't do these NMUs myself if they're
clone 1059165 -1
reassign -1 nodejs
retitle -1 autopkgtest failures on i386
found -1 18.19.0+dfsg-6
block 1059165 by -1
kthxbye
On Wed, Dec 20, 2023 at 08:15:31PM +0100, Paul Gevers wrote:
> The Release Team considers packages that are out-of-sync between testing and
> unstable for more than 30
Chris,
Thanks
On Wed, Dec 06, 2023 at 05:57:55PM +0100, Chris Hofstaedtler wrote:
> * Mark Hindley :
> > On Wed, Dec 06, 2023 at 06:06:41PM +0200, Martin-Éric Racine wrote:
> > > Please note that the start target refers to a non-existing
> > > /usr/lib/udev/rules.d/85-
ystem clock to CMOS.
> Hardware Clock updated to Wed Dec 6 18:05:12 EET 2023.
> [2023-12-06 18:05](HURD i386)perkelix@pxeth:~$ LC_ALL=C sudo
> /etc/init.d/hwclock.sh show
> 2023-12-06 18:05:18.129566+02:00
Thanks. Looks OK to me.
Mark
ck.sh already handles a missing /sbin/hwclock
gracefully.
Mark
commit acdbb98f05db8f24ddc9e72adb2b6a0982e69748
Author: Mark Hindley
Date: Wed Dec 6 10:20:41 2023 +
hwclock.sh: support HURD direct ISA I/O.
Closes: #1057634
diff --git a/debian/src/initscripts/etc/init.d/hwc
Chris,
Thanks for your input.
On Wed, Dec 06, 2023 at 11:56:56AM +0100, Chris Hofstaedtler wrote:
> * Mark Hindley [231206 11:42]:
> > Is hwclock actually useful on Hurd? I (naively) expected it to be linux
> > only. But src:util-linux still ships it[1]. Or is the HCTO
d system usually have util-linux-extra installed or was it only
pulled in by the initscript dependency?
Mark
[1]
https://salsa.debian.org/debian/util-linux/-/blob/master/debian/util-linux-extra.install
Control: tags -1 pending
Helmut,
Many thanks for spotting this.
Queued for next upload.
Mark
tempts on this, Matthew has to say if he's ok
> with maintaining cronjobs in this package and if yes, how this should
> be done.
I think he has already said he isn't happy with that.
I have already submitted a bug with patch to reinstate the cron jobs[1]
alongside the systemd timers.
M
he hwclock machinery
to initscripts, since this is still present in bookworm src:util-linux.
Or, have I misunderstood?
Best wishes,
Mark
diff --git a/debian/control b/debian/control
index 551b7abc..02bfe1b5 100644
--- a/debian/control
+++ b/debian/control
@@ -99,15 +99,12 @@ Multi-Arch: for
I've not been able to start gdm3 for quite a while now.
I've tried upgrading to the latest nvidia driver in experimental
(535.43.02-1) ,
and WaylandEnable=false in /etc/gdm3/daemon.conf
Swapping to the nouveau driver didn't seem to fix it, but then I removed
the WaylandEnable=false and it
ved the udev init script and forced initscripts to take over it was
> already backported.
I have uploaded src:sysvinit 3.08-3~bpo12+1. It is waiting in backports-new[1]
Mark
[1] https://ftp-master.debian.org/new/sysvinit_3.08-3~bpo12%2B1.html
a trip through NEW
2. I suppose somebody may have a use for libelogind0 or libelogind-dev, and I
didn't want to remove that option.
Is that reasonable?
Thanks and best wishes
Mark
Control: tags -1 pending
Thanks.
Queued for the next upload.
Mark
Control: tags -1 pending
Svante,
Many thanks for this. Queued for upload.
Best wishes
Mark
, but protects them
with a test for running systemd. This should mean that housekeeping tasks are
performed an all systems, but that there is no duplication when systemd timers
are available.
I hope this is an acceptable compromise and I look forward to your comments.
With best wishes
Mark
>F
On Tue, Nov 14, 2023 at 03:33:00PM +0100, Helmut Grohne wrote:
> > debootstrap is already broken by the /usr merge, which is something of
> > an annoyance for anyone who uses pbuilder to actually build packages...
> I suspect you are using a bulleye or bookworm system with pbuilder to
> build
On Tue, Nov 14, 2023 at 11:45:35AM +0100, Helmut Grohne wrote:
> fortunately. We do not break the debian-installer (P10), because even
> unmerged chroots have /usr/lib/ on their library search
> paths. I locally verified that we do not break debootstrap (P8) and
> since the affected filename is
t;< 3.0.8-4)
sysvinit-utils without pidof:
Breaks: procps-base (<< 2:4.0.4-3)
I hope I have understood the previous discussions correctly . I am not trying to
stand in the way at all, just ensure that this transition is worthwhile and done
correctly.
With best wishes
Mark
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810018#10
Control: block -1 1055562
Helmut,
On Tue, Nov 07, 2023 at 08:39:23AM +, Mark Hindley wrote:
> I think all suitable dependencies now use default-logind | logind. I will
> check that is correct. If it is, libpam-elogind-compat could just be
> removed. It was never availabl
.
Thanks
Mark
be removed. It
was never available outside experimental.
Mark
ing testsuites. The diff is
attached.
Having said that, I still can't reproduce locally or determine a good fix.
Hopefully Jesse will have a useful contribution
Mark
[1]
https://ci.debian.net/data/autopkgtest/unstable/armel/i/insserv/38435862/log.gz
[2] https://bugs.debian.org/cgi-bin/bugreport.
Lucas,
I am afraid I still cannot reproduce this.
I attach my successful .buildinfo. What are the differences to yours?
Thanks
Mark
Format: 1.0
Source: insserv
Binary: insserv insserv-dbgsym
Architecture: amd64
Version: 1.24.0-1
Checksums-Md5:
3c928ff0990c2942950fa368b3978086 79480 insserv
Supermicro provided a workaround: boot with the kernel command line
parameter pci=realloc=off.
As an side, Rocky 9.2 does not have this issue even though it boots
without that kernel command line parameter.
Jeff (http: //engineering.purdue.edu/~qobi)
Package: linux-image-amd64
Version: 6.4.4-3~bpo12+1
Severity: important
Dear Maintainer,
* What led up to the situation?
I purchased a new server: Supermicro AS-8125GS-TNHR. It has 17 NVME
drives installed:
1x Micron 7450
12x Micron 9300
4x Micron 9400
Upon boot, /dev/nvme* only
by the Policy.
I think this cleanup can happen saftely in the Forky release cycle.
For reference, the udev maintainers have recently tried this cleanup at an
earlier stage and it has not been straightforward.
Mark
by the Policy.
I think this cleanup can happen saftely in the Forky release cycle.
For reference, the udev maintainers have recently tried this cleanup at an
earlier stage and it has not been straightforward.
Mark
Package: python3-xarray
Version: 2023.08.0-1ubuntu5
Severity: normal
X-Debbugs-Cc: mark.harfou...@gmail.com
Dear Maintainer,
* What led up to the situation?
apt install python3-xarray (on ubuntu 23.10). Then
python3 -c "import xarray; assert(xarray.__version__.startswith('201')"
version of json-tricks to be installed.
I am happy to make a merge request directly to
https://salsa.debian.org/python-team/packages/json-tricks
but I don't know if you prefer to rebase or merge when updating your
source.
Thanks!
Mark
-- System Information:
Debian Release: trixie/sid
APT prefers
means to reproduce the bug and a clear justfication for
why I think this is an RC bug. If you disagree, please explain why, rather than
just changing the severity. Thanks.
Best wishes
Mark
diff --git a/debian/changelog b/debian/changelog
index fe1f4bc..ec8a75a 100644
--- a/debian/changelog
+++ b
Control: tags -1 moreinfo
Ian
On Wed, Sep 27, 2023 at 10:33:32PM +0100, Ian Jackson wrote:
> Mark Hindley writes ("Bug#1052942: insserv: FTBFS: insserv: Could not read
> script nolsbheader: No such file or directory"):
> > Thanks for this. However, I am curren
h dropped
/etc/init.d/udev was 254.3-1[1]. AFAICS 254.1-4 was never released.
With best wishes,
Mark
[1] https://tracker.debian.org/media/packages/s/systemd/changelog-254.4-1
> conffile /etc/init.d/udev", but it's still there. However, the
> rc*.d symlinks are not -- "update-rc.d udev defaults" fixes it.
This is a new issue. Cloning.
Mark
r the file and breaks/replaces udev << 254.3-1 ) has migrated to
testing[1], however the migration of src:systemd 254.4-1 is blocked by
autopkgtest regressions[2].
Once a suitable version of src:systemd migrates to testing, I think apt will be
able to resolve the dependencies.
Mark
[1] https://tracker.debian.org/news/1465552/sysvinit-308-1-migrated-to-testing/
[2] https://qa.debian.org/excuses.php?package=systemd
uce this, please provide a build log and diff it with
> mine
> so that we can identify if something relevant changed in the meantime.
My successful pbuilder log is attached.
Mark
[1]
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/insserv.html
dpkg-checkbuilddeps: err
a message popup
> saying
>
> Connection to database foo has failed:
>
> invalid command name "pg_connect"
Thanks. I believe this needs fixing in libpgtcl.
Reassigning.
Mark
to bin:initscripts and
causes non-systemd systems to fail to boot.
Michael, as discussed yesterday on #debian-systemd, I am very grateful for your
quick commit of a fix[2].
This bug is to prevent unintended migration of the broken udev to trixie.
With thanks and best wishes
Mark
[1] https
;Running "dpkg-reconfigure initscripts" did generate the symlinks.
Thanks, that is really useful confirmation that we aren't missing something
else.
Much appreciated.
Mark
On Tue, Sep 19, 2023 at 08:36:05AM +0100, Mark Hindley wrote:
> Yes. I think the real issue is the udev.postinst using update-rc.d -f remove
> udev. Without the -f option, I think the symlinks would be left intact.
The fix for this has been queued in src:systemd[1].
Mark
[1]
mething like
>
> If ! dpkg -s initscripts >/dev/null ; then
> #remove udev 's sysv bits
> fi
Yes. I think the real issue is the udev.postinst using update-rc.d -f remove
udev. Without the -f option, I think the symlinks would be left intact.
Mark
On Tue, Sep 19, 2023 at 07:29:45AM +0100, Mark Hindley wrote:
> > Setting up initscripts (3.08-1) ...
> > Setting up udev (254.3-1) ...
>
> The udev postinst, which removes the update-rc.d symlinks is run after the
> initscripts postinst which has created them.
..
The udev postinst, which removes the update-rc.d symlinks is run after the
initscripts postinst which has created them.
Hmmm...
Mark
Control: tags -1 upstream
Control: forwarded -1 https://github.com/elogind/elogind/issues/263
On Sat, Aug 26, 2023 at 12:03:02PM +0200, наб wrote:
> Package: libelogind-dev-doc
> Version: 246.10-1debian1
> Severity: normal
Thanks. Forwarded upstream.
Mark
Subject: debhelper: dh_installsystemd --name documentation doesn't match actual
behavior
Package: debhelper
Version: 13.11.6
Severity: normal
Dear Debhelper Maintainers,
The dh_installsystemd documentation says that
As an example, B will look for
F<<< IB<< I >>I<.service> >>> instead
re of both util-linux-extra and initscripts having
reciprocal breaks that you identify, it is the recommendation in the Package
Transition Wiki[1]. I think we are dealing with scenario #9.
With best wishes.
Mark
[1] https://wiki.debian.org/PackageTransition
Package: units
Version: 2.22-2
Severity: normal
X-Debbugs-Cc: markgrieve...@yahoo.ca
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I was trying to convert a temperature from degrees Celcius ("degC") to degrees
changes to those files are
correctly preserved.
Can you see any other issues?
Thanks and best wishes
Mark
[1] https://salsa.debian.org/debian/sysvinit/-/tree/wip/udev_initscript
Lorenzo,
On Wed, Aug 23, 2023 at 01:46:35PM +0200, lorenzo wrote:
> Subject: [PATCH 4/5] remove x mode from udev on non-linux archs
>
> initscripts postinst: remove x mode from udev script on non-linux
> archs so that the script is skipped by update-rc.d
> ---
> debian/initscripts.postinst | 5
of course is wrong).
> Anyway I think there need to be some work on udev's side to ensure that
> the udev script is not removed when the initscripts package is
> installed in the system.
Thanks. I also have a pushed a tree[1] for review. I will compare and see if we
have any substantive diff
npage probably contains questionable information.
Thanks. As you say, for the future...
Best wishes
Mark
diff --git a/debian/control b/debian/control
index e3b9c91c..fca27272 100644
--- a/debian/control
+++ b/debian/control
@@ -99,7 +99,10 @@ Multi-Arch: foreign
Depends:
sysvinit-utils (>= 3.05-1),
sy
nsider synchronised uploads to experimental to test and confirm.
Best wishes
Mark
Control: tags -1 pending patch
Lucas,
Thanks for raising this. Fixed version is pending.
Jesse,
My patch for man/Makefile to fix the clean recipe is attached. You may want it,
or something similar, upstream.
Thanks.
Mark
>From 807614887ce310471b72032b4385eed9312acc23 Mon Sep 17 00:00:00 2
On Thu, Aug 17, 2023 at 04:34:56PM +0200, Bastian Germann wrote:
> Am 17.08.23 um 14:25 schrieb Mark Brown:
> > Would it not be more sensible to just require that the format always be
> > specified?
> The problem with that is that most of the implicitly 1.0 packages
On Wed, Aug 16, 2023 at 04:51:44PM +0200, Bastian Germann wrote:
> Am 16.08.23 um 16:40 schrieb Mark Brown:
> > On Wed, Aug 16, 2023 at 04:33:40PM +0200, Bastian Germann wrote:
> > > If you do not want to move to format 3.0, please at least specify 1.0
> > > format
&g
On Wed, Aug 16, 2023 at 04:33:40PM +0200, Bastian Germann wrote:
> If you do not want to move to format 3.0, please at least specify 1.0 format
> so that dpkg-source can move to default 3.0 format.
If you're forcing people to specify the format why does the default
matter?
signature.asc
all and the vast
> > majority of scripts strictly needed to boot and shutdown the system
> > are shipped there.
>
> Wearing my o-s-s maintainer hat, I have no problem with this suggest -
> what do the sysvinit maintainers think?
I can see some logic to this approach.
I am away until next week, but can look at it then.
Mark
- Forwarded message from Mark Hymers -
> Date: Sun, 23 Jul 2023 11:25:21 +0100
> From: Mark Hymers
> To: "Manuel A. Fernandez Montecelo" ,
> 1033658-d...@bugs.debian.orgg
> Cc: Aurelien Jarno
> Subject: Re: Bug#1033658: ftp.debian.org: Please add "
m DSA / buildd etc will
ensure that their sides are done (where needed), that would be helpful.
Once we've had that discussion, I'll add the architecture to the
relevant suites, import the GPG key as a restricted upload key and we
should be good to get started.
Thanks,
Mark
--
Mark Hymers
signatu
1 - 100 of 6065 matches
Mail list logo
